`name` of `cloud.Secret` should refer to an existing name
eladb opened this issue · 2 comments
eladb commented
I tried this
bring cloud;
new cloud.Secret(name: "my-secret-name");
I expected this:
Since name
refers to a physical name, I think it should mean that it references an existing secret instead of trying to create a new one.
If I want a new secret for every app, I expect this behavior:
new cloud.Secret() as "my-secret-id";
And then terraform apply
should output the aws secretsmanager
command for putting the secret value:
aws secretsmanager put-secret-value --secret-id "my-secret-id-129823unb29438723" --secret-string "STRING"
Instead, this happened
Since this is a physical name, it means that it is impossible to deploy multiple instances of the app (e.g. with wing test
), and generally it's a hassle.
Is there a workaround?
No response
Component
SDK
Wing Version
No response
Wing Console Version
No response
Node.js Version
No response
Platform(s)
No response
Anything else?
No response
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.
jogold commented
What would be the syntax to provision a new secret with a defined name then?
monadabot commented
Congrats! 🚀 This was released in Wing 0.13.24.