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

Hide verify-connection attribute on connection config show page #13152

Merged
merged 2 commits into from
Nov 16, 2021

Conversation

hashishaw
Copy link
Contributor

@hashishaw hashishaw commented Nov 15, 2021

Fixes a misleading UI where verify_connection value is shown on the database secrets engine connection show page, where it is never returned from the API. Issue #13119 is related to this fix.

verify_connection is only used when saving the connection, so it isn't stored with the other attributes and shouldn't be shown on the connection page.

Before, after unchecking "Verify connection":
Screen Shot 2021-11-15 at 4 35 11 PM

After, on same connection:
Screen Shot 2021-11-15 at 4 34 54 PM

@hashishaw hashishaw added ui backport bug Used to indicate a potential bug labels Nov 15, 2021
@hashishaw hashishaw added this to the 1.8.6 milestone Nov 15, 2021
@vercel vercel bot temporarily deployed to Preview – vault November 15, 2021 22:41 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook November 15, 2021 22:41 Inactive
@hashishaw hashishaw merged commit b8b0ad1 into main Nov 16, 2021
@hashishaw hashishaw deleted the ui/hide-verified-connection-attr branch November 16, 2021 18:56
hashishaw added a commit that referenced this pull request Nov 16, 2021
* Hide verify-connection attribute on connection config show page

* Add changelog
hashishaw added a commit that referenced this pull request Nov 16, 2021
* Hide verify-connection attribute on connection config show page

* Add changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport bug Used to indicate a potential bug ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants