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

[Question] is it possible to set labels on a AzureKeyVaultSecret #65

Closed
floriankoch opened this issue Apr 9, 2020 · 2 comments
Closed
Labels
question Further information is requested

Comments

@floriankoch
Copy link

floriankoch commented Apr 9, 2020

Hi,

ist it possible to set a label on a secret ressource?

e.g.

apiVersion: spv.no/v1alpha1
kind: AzureKeyVaultSecret
metadata:
  name: < name for azure key vault secret>
  namespace: <namespace for azure key vault secret>
spec:
  vault:
    name: <name of azure key vault>
    object:
      name: <name of azure key vault object to sync>
      type: <object type in azure key vault to sync>
      version: <optional - version of object to sync>
      contentType: <only used when type is the special multi-key-value-secret - either application/x-json or application/x-yaml>
  output: # ignored by env injector, required by controller to output kubernetes secret
    secret: 
      name: <name of the kubernetes secret to create>
      label: mylabel
      dataKey: <required when type is opaque - name of the kubernetes secret data key to assign value to - ignored for all other types>
      type: <optional - kubernetes secret type - defaults to opaque>
´´´
@floriankoch floriankoch added the question Further information is requested label Apr 9, 2020
@torresdal
Copy link
Collaborator

No. But feel free to convert this to a feature request 😃 ...or a pull request 👨‍💻

@torresdal
Copy link
Collaborator

Feature suggested in #104 - closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants