fixing default attributes based on HWRP #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Commit looks good to me. The tests failing are not relevant to this PR. |
acaiafa
added a commit
that referenced
this pull request
Jul 31, 2015
fixing default attributes based on HWRP
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There were two default attributes that might have been missed on the last rework of the vault_config HWRP.
attribute(:address, kind_of: String) # formerly :listen_addressattribute(:tls_disable, kind_of: String, default: "")Based on this information I removed the tls_disable default as it was a bool and we are expecting a string, in addition we default that string in the provider.
listen_address was also updated based on the comments.
As always, great work on this cookbook @johnbellone.