This message was deleted.

sparse-intern-71089

06/25/2020, 11:33 PM

This message was deleted.

billowy-army-68599

06/25/2020, 11:40 PM

if you're using the same state yeah. Generally you'd login to the same state backend, and then name your project something like `<project>.<envrionment> - so vpc.producton You can then reference your stack in a similar way to the app.pulumi.com backend

little-cartoon-10569

06/25/2020, 11:43 PM

Hmm. I infer from that that I've been using backend urls incorrectly... I'm logged into app.pulumi.com, and my Pulumi.yaml files all include bits like this:

Copy code

backend:
  url: <s3://mypulumibucket/pulumi/thisproject>

So there's no relationship between projects via the login, it's all done via a common s3 bucket....

little-cartoon-10569

06/25/2020, 11:52 PM

To get what I want, I would have to use one file in my bucket for all project states:

Copy code

backend:
  url: <s3://mypulumibucket/pulumi>

Which would mean I'd need stricter locking. But Pulumi can handle multiple projects and stacks in a single state file, so long as the locking is handled for it. I think I'll wait until we move to app.pulumi.com (or self-hosted) before doing that. Which means waiting until it's more entrenched here so that no one tells me to stop using it and to go back to Terraform 😉

Open in Slack

Previous Next

Pulumi Community

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.