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

Also, what is the difference between Pulumi Enterprise and `pulumi login --local`?

This in general is one for <@UDEJ1F5SQ> or <@U84SY03DF> I think - but the essential difference is whether you have a copy of the service, or just manage state files on local disk

so we could use local to trial pulumi with our secrets until we are comfortable enough to go for the web or enterprise product

i'm using it with local state files where the only thing with required deploy keys is the CI server and a script to get and push state from git

configured to only allow one build thread at a time and running pulumi preview as the PR validation then pulumi up as the CI merge

The Pulumi SaaS (Team and Enterprise) provides a web console, state storage, collaboration, teams, role-based access control, SAML, etc. The full feature breakdown is at <https://www.pulumi.com/pricing/>.

Note: you can use the Community tier for free to try out Pulumi too! Easier to get up and running that way. :slightly_smiling_face:

<@UDEJ1F5SQ> thanks.  we are more concerned about the storage of secrets than anything.  hoping to use the local backend to get a feel for how things are stored without inadvertently exposing anything

Understood. FYI, we are working on making the secret storage pluggable at the client, so secrets are never visible to the SaaS. <https://github.com/pulumi/pulumi/issues/1547>