Is it possible to prevent (accidental) uncommitted...
# general
Is it possible to prevent (accidental) uncommitted deploy ? Something in Pulumi teams or crossgaurd would be okay too. I see on the pulumi site that pulumi keeps track of when you run
pulumi up
on uncommitted code
Hmm, that's an interesting idea. There's nothing built in, but I think a custom policy check could do it.
@mammoth-elephant-55302 like Cameron said, there isn’t anything built-in that can do that now. But the idea has come up before. Can you elaborate on what you mean by “uncommitted deploy”? Would it be sufficient to just see if the
worktree is dirty or not? (i.e. any files under source control were modified, or new files locally but not in the repo.)
Yes I think that would be helpful