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

I’m trying to create a pulumi provider base on a existing terraform provider. I’m lost in one of the step that is asking that
```1. Create an account with the provider's service and generate any necessary credentials, e.g. API keys.
    - Email: &lt;bot@pulumi.com&gt;
    - Password: (Create a random password in 1Password with the  maximum length and complexity allowed by the provider.)
    - Ensure all secrets (passwords, generated API keys) are stored in Pulumi's 1Password vault.```
How can I stop that in pulumi 1password vault :thinking_face:

Oh that's for when we're bridging to remind our engineers to put the passwords where we can all access them. For your own bridged provider you'll want to make your own account to test with (not <mailto:bot@pulumi.com|bot@pulumi.com>) and keep those passwords yourself whereever that makes sense.