Well, that's good. Since last week I've been working on a thing that sends emails at the end of a Chef run, either confirming that everything happened as expected or advising of any epic fail that transpired.
I've got all the bits working and finally come to the point where I want to test the actual sending of the email. So I go to find out what SMTP server I should be using, and what credentials to supply, and so forth.
Turns out the email server available for such purposes has a whitelist of IP addresses that are allowed to use it. But as Chef, by definition, is adding a new host, its IP address can't possibly be on that list. So it can't send email.
After some discussion, the consensus seems to be that this cannot possibly work as intended
I'm just going to record it as a blocker and finish what I'm doing anyway. At least that way, if the company ever completely changes its entire IT security process, it should work straight away. More to the point, I can still invoice
I've got all the bits working and finally come to the point where I want to test the actual sending of the email. So I go to find out what SMTP server I should be using, and what credentials to supply, and so forth.
Turns out the email server available for such purposes has a whitelist of IP addresses that are allowed to use it. But as Chef, by definition, is adding a new host, its IP address can't possibly be on that list. So it can't send email.
After some discussion, the consensus seems to be that this cannot possibly work as intended
I'm just going to record it as a blocker and finish what I'm doing anyway. At least that way, if the company ever completely changes its entire IT security process, it should work straight away. More to the point, I can still invoice
Comment