Channels
esc
welcome
pulumi-cdk
cloudengineering
yaml
blog-posts
localstack
pulumi-ai
package-authoring
policy-as-code
pulumiup-booth-support
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
gitlab
general
pulumi-kubernetes-operator
jobs
pulumi-deployments
dotnet
aws
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
Powered by
#general
Title
# general
s
straight-cartoon-24485
09/27/2023, 10:50 PM
How are dynamic providers supposed to use Pulumi secrets?
Configuration
A provider may accept a set of configuration variables. After a provider is instantiated, the instance must be configured before it may be used, even if its set of configuration variables is empty. Configuration variables may be of
any type
.
Because it has no connection to the Pulumi engine during configuration, a provider’s configuration variables should not rely on the ability to resolve
resource references
.
ref:
https://pulumi-developer-docs.readthedocs.io/en/latest/providers/implementers-guide.html?highlight=secrets#configuration
Are secrets resolvable through resource references? The only example I found seems to pass secrets in plain text:
https://github.com/pulumi/examples/blob/2f0bd7762d6c8597066a2b9725e4b155f1d2035c/aws-py-dynamicresource/__main__.py#L101C7-L101C7
Post