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

Hello,
I am looking for secret management options for pulumi apart from default service which pulumi provides. What is mostly used or preferred? Some things which we have currently are below:
• Vault
• GitHub secrets
• AWS secret manager
• 1password/secrets
Any document or experience someone can share would be great as we have recently started using pulumi.

I don't believe we have 1password provider support yet, but I'd love to know more about your use case

1. To store secrets required for deploying a server in hetzner cloud e,g hcloud token, AWS secret and Access for state file, Github Oauth KEY and ID for GH as auth provider in rancher etc.
2. Once rancher is installed using pulumi we would need to set some management there, currently using vault and for basic secrets rancher/kubernetes secrets can be used.

I am not sure if for both these scenario 2 separate management would be needed or we can do it together.

Currently, for pulumi I have saved everything in Github secrets that are fetched in GitHub actions as ENV values.