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

Support custom labels on created Secret #64

Open
aarguello opened this issue Jun 25, 2024 · 3 comments · May be fixed by #67
Open

Support custom labels on created Secret #64

aarguello opened this issue Jun 25, 2024 · 3 comments · May be fixed by #67

Comments

@aarguello
Copy link

Problem

The DopplerSecret CRD does not have a field to set labels on the Secret it manages. This prevents me to manage ArgoCD cluster and repository credentials using Doppler because ArgoCD determines a secret's purpose based on its label, particularly argocd.argoproj.io/secret-type: cluster | repository | repo-creds.

Proposal

Add a labels field under managedSecret, so that I could declare something like the following:

apiVersion: secrets.doppler.com/v1alpha1
kind: DopplerSecret
metadata:
  namespace: doppler-operator-system
  name: argocd-cluster-credentials
spec:
  tokenSecret:
    name: doppler-token-secret-argocd
  managedSecret:
    name: argocd-cluster-credentials
    namespace: argocd
    labels:
      argocd.argoproj.io/secret-type: cluster

Another alternative would be to replicate the labels of the DopplerSecret to the Secret.

Please let me know if you think this feature makes sense and, if it does, whether you'd like me to send a PR for it or prefer that the project maintainers handle it.

References

@nmanoogian
Copy link
Member

Thanks for the recommendation, @aarguello! I like your initial proposal for defining labels on the managedSecret object. If you're up for it, a PR for this feature would be much appreciated!

@Lp-Francois
Copy link

I was running into the exact same issue!

It would be nice to support annotations as well.

@aarguello
Copy link
Author

I'll set aside some time next week to submit a PR!

@tommatime tommatime linked a pull request Aug 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants