https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
if you only have a single person working on it, checking into git is fine If you have multiple people doing deployments, the state being in git is going to cause a lot of issues
✅ 1
m
All deploys will be through pull requests with a pipeline executing them. I guess so long as only one instance of the pipeline actually runs 
pulumi up
we are going to be fine?
I have storage accounts and such ready for Azure, I just wish there was a way to access it without a storage key or sas token (e.g. simply using the principal with the right role assigned to it and have pulumi work its magic in the background instead of having to have keys in the pipeline which eventually gets rotated).
b
i think so. I wouldnt do it myself
m
Well, thats good enough for me to not do it the git way then 👍
f
the 
pulumi up
is going to write to state… so you would have to commit your code changes, 
pulumi up
, and then commit the resulting state json changes. Theoretically viable but you might have to block merges to your main branch to avoid race conditions
✔️ 1
m
Right, that makes sense. Not what I want to do.
15 Views
Open in Slack
PreviousNext
Powered by

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.

Powered by