Update Prefixes not allowed in secrets-management #6705
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add some more prefixes that we found out was not allowed
jesp209i
changed the title
eshanrnh
reviewed
Nov 27, 2024
Co-authored-by: Esha Noronha <82437098+eshanrnh@users.noreply.github.com>
eshanrnh
approved these changes
Nov 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
I have added more prefixes that are not allowed to be used with
Secrets Management.Can you help write in a nice way that the list most likely is not complete?
Type of suggestion
Product & version (if relevant)
Cloud / Secrets Management
Deadline (if relevant)
when you have time 🥇