https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
m
What do you use as secret backend? If it is AWS Secrets Manager, you need to retrieve a secret version using 
aws.secretsmanager.getSecretVersion
. The returned object has the secret as 
secretString
or 
secretBinary
depending which one you used to store it.
f
I am just Using pulumi as is with their backend.
I thought this was abstracted over
m
Yeah, I figured that out while rereading your post 🤦‍♂️
f
I mean using the aws secret manager does seem to do what I expected the config.Secret stuff to do.
m
The pulumi secrets are fetched using:
Copy code
const config = new pulumi.Config();
config.getSecret('my_secret');
or
Copy code
config.requireSecret('my_secret');
These secrets are stored encrypted in your 
Pulunmi.<stack-name>.yaml
file in the root of your pulumi project.
f
Yeah and if it’s empty, you can set them. But you don’t get to offer a key to lookup on next runs
@microscopic-dress-1605 Our yaml files are ephemeral. We don’t store them.
The docs make it sound like it has runtime support
m
There I lack knowledge. Sorry.
f
No worries, I appreciate it. At least I can generate my keys now 🙂
Seems like Pulumi is missing a “cache” of some sort that’s created at runtime.
cache.addOrGet("key", "value")
that also supports secrets.
11 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by