-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Add snowflake DB API warning #30327
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 snowflake DB API warning #30327
Conversation
Build Results: |
CI Results: |
website/content/partials/deprecation/snowflake-password-auth.mdx
Outdated
Show resolved
Hide resolved
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.
LGTM, but had a few more thoughts:
Should we also add a notice at the top of the Snowflake overview page here https://vault-oj7azsli6-hashicorp.vercel.app/vault/docs/secrets/databases/snowflake and on the API page here https://vault-oj7azsli6-hashicorp.vercel.app/vault/api-docs/secret/databases/snowflake?
Also, maybe we should mark the Capabilities table entries for password as deprecated?
* Add API warning based on DB type * Add deprecation notice * Add warning to the top of the docs pages * Update capabilities table * Filter SQLConnectionProducer fields from unrecognized parameters warning * Add test case
* Add API warning based on DB type * Add deprecation notice * Add warning to the top of the docs pages * Update capabilities table * Filter SQLConnectionProducer fields from unrecognized parameters warning * Add test case
Description
Adds warnings for newly created or updated snowflake DB secrets configs for the removal of password authentication.
TODO only if you're a HashiCorp employee
backport/
label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x
, but older release branches will bebackport/ent/x.x.x+ent
.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.