-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
vault_secret: Save lease ID to the nested attribute #56
Conversation
It allows to avoid conflicts with other top-level attributes.
Great! One small suggestion. Should we expose this as a property and have its default value come from an attribute? |
I've made a mistake in the PR title. In fact, we use node attributes only to save secret lease ID, not the entire secret. So, this attribute is designed only for the internal technical reason - to validate lease ID in upcoming Chef client runs. IMO, there is no need to customize this property. However, it is reasonable to make run_state nesting level customizable, because that's exactly how users access secrets in the recipe code. In this PR I haven't touch it: |
True, but we are storing something on node object, and it would be nice to let people change it if they wish (perhaps there is another use we're not thinking of). However, this can always be added later. I agree with making the reference in run_state customizable. One way would be to change |
Current coverage is 52.58%@@ master #56 diff @@
========================================
Files 2 2
Lines 97 97
Methods 0 0
Branches 0 0
========================================
- Hits 72 51 -21
- Misses 25 46 +21
Partials 0 0
|
@Ginja I'va added resource property |
Looks great. Thanks! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
It allows avoiding conflicts with other top-level attributes.
Related comment: 7f2f49d#commitcomment-17324222
cc: @Ginja