Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
f
full-dress-10026
05/03/2022, 9:01 PMHi. I have some code that stores API tokens in AWS SSM. During a pulumi update, I issue a call to SSM to get the secret value using
aws.ssm.getParameterpulumi.output(resp).apply(r => r.value)Working this back a bit more by ssh'ing into CI, I see it's returning version 1 of the parameter when there is a version 2.
Why would pulumi return a parameter version that is not the latest?
Even after deleting the version 1 parameter, pulumi still returns the version 1 result 🤯 There must be some sort of caching coming into play...
q
quick-airport-30353
05/03/2022, 9:39 PMdumb question, why not use pulumi set config --secret <Your secret value>?
f
full-dress-10026
05/03/2022, 9:45 PMOH, I see. The aws.ssm.getParameter call is ignoring the aws:profile set in the pulumi yaml file! The call is going to the wrong account.