Search code examples
infrastructurepulumiinfrastructure-as-code

Locking of pulumi stacks


I am new to Pulumi. Is there any option to lock a particular stack in Pulumi to prevent accidental updates or deletion? I understand that RBAC is enforced to provide this functionality to only members with required permissions.However, I still want to prevent accidental changes to the stack even when the persons with all necessary permissions attempt to do it.


Solution

  • You're correct in that only members of teams with the correct permissions on stacks can update them or destroy them. There's no way to lock a stack.

    What I would do is have a separate stack for your production deployment and then only give access to your CI/CD pipeline tool of choice so that no one else can do the update.

    This is also why Pulumi has previews so that you can see what is being changed before you agree to the update.

    Recently, Pulumi announced "Update Plans" (blog post announcing this: https://www.pulumi.com/blog/announcing-public-preview-update-plans/) that might help you out.