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

Just wanted to see if anyone else is experiencing this:

When using pulumi config `aws:accessKey` + `aws:secretAccessKey` - these values work and are mostly respected when running `pulumi up`, but appear completely ignored when running `pulumi down`