You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We enforce randomness on our resources. Lets assume we generate a SQL database called sql-37fjs29sw and some secrets along with the db sql-37fjs29sw. If we would re-create the database or deploy to a different stage, the random part of the name would change and we have to update the definition of AKV2AKS secret.
Describe the solution you'd like
If we could select secrets by tags we could tag the secrets accordingly and deploy the same AKV2AKS manifest in all stages without changing the secret name.
Example:
apiVersion: spv.no/v2beta1 # custom resource definition versionkind: AzureKeyVaultSecretmetadata:
name: foonamespace: defaultspec:
vault:
name: mykvobject:
tags:
- name: appvalue: myapp1type: secretoutput: # ignored by env injector, required by controller to output kubernetes secrettransform: # optional transformers executed in listed order
- trim # optional - trims empty space
- base64encode # optional - encode to base64
- base64decode # optional - decode from base64secret:
name: <name of the kubernetes secret to create>type: <optional - kubernetes secret type - defaults to opaque>dataKey: <required when type is opaque - name of the kubernetes secret data key to assign value to - ignored for all other types>chainOrder: <optional - used when server certificate is at the end of the chain - set to ensureserverfirst>configMap:
name: <name of the kubernetes secret to create>dataKey: <name of the kubernetes config map data key to assign value to>
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We enforce randomness on our resources. Lets assume we generate a SQL database called
sql-37fjs29sw
and some secrets along with the dbsql-37fjs29sw
. If we would re-create the database or deploy to a different stage, the random part of the name would change and we have to update the definition of AKV2AKS secret.Describe the solution you'd like
If we could select secrets by tags we could tag the secrets accordingly and deploy the same AKV2AKS manifest in all stages without changing the secret name.
Example:
The text was updated successfully, but these errors were encountered: