-
Notifications
You must be signed in to change notification settings - Fork 18
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 support for custom managed secret types #47
Conversation
aef1784
to
87b375d
Compare
Wow at first glance over the changes and doc, this is an amazing change/update. May do exactly what I needed |
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.
Nice docs!
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.
Looks good to me. I just have some minor nitpicks, but mergeable as is. I don't see any tests for this change, how do we test changes to the operator?
Awesome! Thanks for calling those out. I'll make the changes.
Great question -- our tests for the operator are definitely lacking and most of my testing for this change has been manual. I'd love to pick your brain on ways that we could add automated tests for this functionality! |
- Split token secret ref and manage secret ref CRD model types - This allows managed secret ref to supports an optional `type` field - Add `asName` field to processor, allowing for name transformation - Allow processor `type` field to be optional, defaulting to "plain"
87b375d
to
145f8d1
Compare
This PR adds custom Kubernetes secret types to the operator. The README and docs changes describe the use cases and behavior changes.
Closes ENG-6130