This feature refines auto-approval of infrastructure provisioning to match user behavior better.
Originally, we required every plan to go through approval; however, this was extremely distracting for users launching new infrastructure. In essence, users would ask "Didn't I just approve it when I clicked 'Launch'?" To remediate, Nullstone auto-approved every plan. When destroying, Nullstone prompted for approval before running the plan.
Intended Outcome
Blocks that have status not-provisioned are auto-approved
Destroy plans require approval from stack architect.
Summary
This feature refines auto-approval of infrastructure provisioning to match user behavior better.
Originally, we required every plan to go through approval; however, this was extremely distracting for users launching new infrastructure. In essence, users would ask "Didn't I just approve it when I clicked 'Launch'?" To remediate, Nullstone auto-approved every plan. When destroying, Nullstone prompted for approval before running the plan.
Intended Outcome
not-provisionedare auto-approvedHow will it work?