12/17/2021, 5:28 PM
I have a local helm template I've rendered. Before I get too deep into helm I want to evaluate Pulumi for creating a common module instead. Here's the piece I'm not clear on. I know I'd need to use remote state for the shared staging environment. For devs locally though I want to be able to run the local docker/k8 definitions and spin up containers and such. I'm not clear on how local dev/testing is handled, so that they aren't needing to store state remotely and just using for free in local context. Any tips on this? Go with K8 + Azure seems promising but need to make I'm not having to maintain local + remote configurations.


12/17/2021, 6:19 PM
@chilly-plastic-75584 happy to jump on a call to discuss this, but generally orgs use pulumi's individual accounts if there's no desire to share the state.
it's free for individuals, so they can spin up workflows to their hearts content
you can also do per user stacks


12/17/2021, 10:54 PM
cool. Might do that once I get the final steps running with helm. Having a local dev workflow involved in logging into pulumi vs just running in local context might be problematic, but not sure yet. Sounds like for local test/ephemeral environments I still need to use remote state primarily to keep it simple right?