-
Notifications
You must be signed in to change notification settings - Fork 423
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
Chef >= 11.14.0 requirement #183
Comments
Those updates look reasonable to me. Thanks |
Apologies for revoking a closed thread, but can you please give me some pointers on how should those stuck with Opsworks use this? As in, we are still stuck with Chef version 11.10, which we know is "old" now :( |
Honestly, you'll have to fork an older version that worked with Opsworks and support it yourself. The scope of this cookbook is the versions we say we support and running Chef not opsworks. |
It's a pity that you ditched the Opsworks support just to use 'sensitive' in execute block. |
Although the feature isn't backwards compatible, I believe the tradeoffs are important. Displaying plaintext passwords anywhere is a serious issue. I don't believe that this cookbook is incompatible with opsworks due to the sensitive parameter, rather just incompatible with chef < 11.14. |
The user provider leverages a relatively new attribute on an execute block (sensitive). This makes a ton of sense, but the challenge here is that was only introduced in 11.14.0 which has been out "all that long". At the very least I think the README needs to call out the Chef version as a requirement. It would be even more awesome, if a check was done for Chef version and only use sensitive on versions that support it.
The text was updated successfully, but these errors were encountered: