Skip to content
GantryCD

Trigger policies

Set trigger on a dependency declaration:

# gantrycd:dependency: from_stack=network trigger=always
  • manual is the default. GantryCD offers a deployment for someone to start.
  • always starts a plan deployment automatically.
  • never records the relationship without offering or starting a deployment.

Triggers are resolved after a successful apply in a normal plan deployment. Pull request promotions and destroys do not trigger dependents.

A declaration with from_resource is considered only when that resource or output changed in the applied plan. A whole-stack declaration is considered for any change.

An automatic deployment uses the dependent stack’s configured branch. It also follows that stack’s approval settings, so it may apply without another review.

When several matching policies disagree, manual wins over never, and never wins over always. A declaration for the whole dependent stack takes priority over declarations on its individual resources. GantryCD also changes always to manual when it cannot prove that automation is safe, such as for a dependency cycle or incomplete dependency data.