Background
When the Integrated Benchling Webhook is not enabled, the current behavior is to handle it automatically, which can lead to stack drift.
Proposed Behavior
- Check if the required configuration is enabled
- Tell the user to ask IT to enable it via their IaC config (e.g., CloudFormation, Terraform)
- Optionally allow rerunning with
--force if absolutely necessary
Rationale
Most customers manage their stacks via IaC tooling. The correct path is to:
- Escalate to IT so they can adjust the IaC config and apply the change
- Avoid making ad-hoc changes that bypass IaC state
Although this is an inconvenient UX ("First, wait for your IT department to do something"), it prevents stack corruption and aligns with how customers actually manage infrastructure.
References
Background
When the Integrated Benchling Webhook is not enabled, the current behavior is to handle it automatically, which can lead to stack drift.
Proposed Behavior
--forceif absolutely necessaryRationale
Most customers manage their stacks via IaC tooling. The correct path is to:
Although this is an inconvenient UX ("First, wait for your IT department to do something"), it prevents stack corruption and aligns with how customers actually manage infrastructure.
References