chore: add sensitive flag for password kind settings #1696
Merged
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.
The SDK metadata refresh automation has updated all password kind settings to include the sensitive flag but that doesnt consider non-SDK variants, this PR handles those. We started to get individual PRs like #1693 and #1692 to add the sensitive flag so clearly users are wanting the flag to be updated (presumably to get rid of warning logs) so I figured its good to get all plugins updated.