-
Notifications
You must be signed in to change notification settings - Fork 123
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
Aws secretmanager secret creation from a kubernetes secret doesn't transfer all keys of k8s secret to the aws secret #783
Comments
The way I've managed to get this working is to construct a kubernetes secret with a single key, whose value is a stringified json object containing all the key:value pairs I want to be in secretsmanager. This is not the most intuitive interface, but it works. |
Thanks for your reply. In our case we really want to push a TLS secret which is automatically created by cert manager. So we dont have control on the data structure of this secret . |
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
+1 , this is very annoying, can we maybe open a feature request to make the secretStringSecretRef.key optional and if not exist push the whole secret in a key value format just like in the opensource crossplane provide? |
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
This issue is being closed since there has been no activity for 14 days since marking it as |
+1 |
1 similar comment
+1 |
Upbound provider : 0.37
Crossplane version : 1.12
Trying to create a secret manager secret using the following yaml .
My kubernetes secret has 2 fields called test and test1.
The first problem here is that the key is mandatory unlike opensource crossplane provider where key is optional(https://doc.crds.dev/github.com/crossplane/provider-aws/secretsmanager.aws.crossplane.io/Secret/[email protected])
In the opensource provider if we dont provide the key it creates the whole secret on AWS secret manager with all present keys in the secret. This is very useful when we use tls secrets with certificates.
The second issue is that when we try to do both keys in the secret it only puts last operations value in aws. We tried to add the second key as follows. But then it overrides the previous one and i can see only test1 value on AWS console.
So in short we are unable to push multi key-value secrets to AWS secret manager.
The text was updated successfully, but these errors were encountered: