Problem description
The documentation does not describe the canonical, supported way to trigger downstream stack updates when an upstream stack changes. Lacking this, users build webhook workarounds that misbehave — in one reported case the workaround fired ~50x and re-triggered repeatedly. Deployment Triggers and StackReference exist, but neither documents the recommended pattern for cascading a deploy to dependent stacks without duplicate fires or loops.
Suggestions for a fix
Write a guide showing the recommended pattern for triggering dependent stack updates, with explicit guidance on avoiding duplicate fires and re-trigger loops. Contrast it with the naive webhook approach so users know what to avoid.
Reported from customer feedback on a Clari call (internal). Source: Slack thread.
Problem description
The documentation does not describe the canonical, supported way to trigger downstream stack updates when an upstream stack changes. Lacking this, users build webhook workarounds that misbehave — in one reported case the workaround fired ~50x and re-triggered repeatedly. Deployment Triggers and StackReference exist, but neither documents the recommended pattern for cascading a deploy to dependent stacks without duplicate fires or loops.
Suggestions for a fix
Write a guide showing the recommended pattern for triggering dependent stack updates, with explicit guidance on avoiding duplicate fires and re-trigger loops. Contrast it with the naive webhook approach so users know what to avoid.
Reported from customer feedback on a Clari call (internal). Source: Slack thread.