Skip to content
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

Re-add mount plugin name for backwards compatibility #5807

Closed
wants to merge 1 commit into from

Conversation

tyrannosaurus-becks
Copy link
Contributor

This PR re-adds the PluginName field on the MountConfig in case it comes back to the current Vault client from an older Vault server.

Copy link
Contributor

@catsby catsby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems legit, but need to verify this is the direction to take. #5797 seems to still be under discussion

@@ -164,6 +164,7 @@ type MountConfigOutput struct {
DefaultLeaseTTL int `json:"default_lease_ttl" mapstructure:"default_lease_ttl"`
MaxLeaseTTL int `json:"max_lease_ttl" mapstructure:"max_lease_ttl"`
ForceNoCache bool `json:"force_no_cache" mapstructure:"force_no_cache"`
DeprecatedPluginName string `json:"plugin_name,omitempty" mapstructure:"plugin_name"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I would rather have PluginName and a comment above documenting that it's deprecated but kept for BC reasons, and to use Type instead.

@tyrannosaurus-becks
Copy link
Contributor Author

Closing in favor of #5825

@briankassouf briankassouf deleted the auth-secrets-list-compat branch November 20, 2018 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants