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.

Pulumi Community

another related question: i use `pulumi stack init $STACK_NAME --secrets-provider="awskms://$SECRETS_KEY_ALIAS?region=$AWS_REGION"` from within the CI. This stores the secrets-provider into the stack configuration file. I don't want to have to check-in this stack configuration file, because it's running in the CI. Is there a way to regenerate the stack configuration file with the secrets provider configuration upon every run?

ok, found some info <https://github.com/pulumi/pulumi/issues/7282|here>. Normally `pulumi config refresh -s $STACK_NAME` should do this :crossed_fingers: let's see. It tells me `error: no previous deployment` for now but I need to test when actually deploying something.

ok I got`refreshed configuration for stack 'dev'` and I can then run it so I guess it's working