-
-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sasl passwd problems with 5.3.0 #148
Comments
we ran into same issue. it broke our deployment.
|
+1 . This should be caught by unit tests :) |
I was about to post this issue, but found it is already posted. node.default_unless['postfix']['sasl']['smtp_sasl_user_name'] = ''
node.default_unless['postfix']['sasl']['smtp_sasl_passwd'] = '' in node.default_unless['postfix']['sasl'] = {} This will eliminate the lines:
The actual configuration, as @fletchowns indicated should be: default["postfix"]["sasl"] = {
"email-smtp.us-east-1.amazonaws.com:587" => {
"username" => "<snip>",
"password" => "<snip>"
}
} This needs to be updated in documentation as well. |
Instead of
Then anywhere in your wrapper cookbook, edit the template resource: edit_resource!(:template, node['postfix']['sasl_password_file']) do
variables(settings: node['my-cookbook']['sasl'])
end You'll end up with the right file:
Hopefully it helps! 👨🍳 |
Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs. |
it's still an issue 😅 |
Cookbook version
5.3.0
Chef-client version
12.20.3
Platform Details
Red Hat Enterprise Linux Server release 7.5 (Maipo) on AWS
Scenario:
smtp relay host via SES with sasl uesrname & password
Steps to Reproduce:
I had been using this for awhile in my attributes:
Expected Result:
Previously, this seemed to result in:
Actual Result:
Now with 5.3.0 I ended up with:
I was able to resolve it by changing the attributes:
It seems like it was a breaking change with a minor version bump though
The text was updated successfully, but these errors were encountered: