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 support for custom managed secret types #47

Merged
merged 2 commits into from
Aug 14, 2023
Merged

Conversation

nmanoogian
Copy link
Member

@nmanoogian nmanoogian commented Aug 4, 2023

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

@emmeowzing
Copy link

Wow at first glance over the changes and doc, this is an amazing change/update. May do exactly what I needed

Copy link

@Piccirello Piccirello left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice docs!

Copy link

@seslattery seslattery left a 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?

controllers/dopplersecret_controller_secrets.go Outdated Show resolved Hide resolved
controllers/dopplersecret_controller_secrets.go Outdated Show resolved Hide resolved
controllers/dopplersecret_controller_secrets.go Outdated Show resolved Hide resolved
@nmanoogian
Copy link
Member Author

Looks good to me. I just have some minor nitpicks, but mergeable as is.

Awesome! Thanks for calling those out. I'll make the changes.

I don't see any tests for this change, how do we test changes to the operator?

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"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants