-
Notifications
You must be signed in to change notification settings - Fork 549
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
Add support for configuring username and password fields for select DB Engines #1331
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks Great!
resource.TestCheckResourceAttr(testDefaultDatabaseSecretBackendResource, "data.%", "2"), | ||
resource.TestCheckResourceAttr(testDefaultDatabaseSecretBackendResource, "data.username", testUsername), | ||
resource.TestCheckResourceAttr(testDefaultDatabaseSecretBackendResource, "data.password", testPassword), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So these are unrelated to this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are to be removed since username and password are now being set on the resource config itself, though how these data fields are passed to Vault, I am slightly unclear on
- ensure related MySQL tests run in CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ship it!
This PR adds support for configuring the
username
andpassword
fields in Vault through the Provider for all DB Engines that support those fields (all DBs except MongoDB Atlas)Relates OR Closes #1314 #1329
Release note for CHANGELOG:
Output from acceptance testing: