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

Add a typeMatcher for Secrets #961

Open
jorgemoralespou opened this issue May 22, 2024 · 0 comments
Open

Add a typeMatcher for Secrets #961

jorgemoralespou opened this issue May 22, 2024 · 0 comments
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@jorgemoralespou
Copy link

Describe the problem/challenge you have
There's certain behavior that depends on the type of the secret (and potentially other objects that provide a type field). Current matchers don't allow to select only these resources. You need to resort to possible annotations present in these objects.

Describe the solution you'd like
A resource matcher that could match also by type, so that you could do explicit rules for the different kind of secrets


Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

@jorgemoralespou jorgemoralespou added carvel triage This issue has not yet been reviewed for validity enhancement This issue is a feature request labels May 22, 2024
@renuy renuy moved this to To Triage in Carvel May 24, 2024
@renuy renuy added carvel accepted This issue should be considered for future work and that the triage process has been completed and removed carvel triage This issue has not yet been reviewed for validity labels May 24, 2024
@renuy renuy moved this from To Triage to Unprioritized in Carvel May 24, 2024
@renuy renuy added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
Status: Unprioritized
Development

No branches or pull requests

2 participants