In Flashduty On-call
- In the Flashduty console, go to Integration Center → Change Events
- Select Alibaba Cloud DevOps AppStack and enter an integration name
- To assign changes to specific channels, add rules under the integration’s Routes that match labels such as
apporenvironment - Click Save and copy the generated Push URL
Configure AppStack
1
Create a webhook
- Global webhook (applies to every application in the organization): on the AppStack home page, go to Global Settings → Webhooks and click New Webhook
- Application webhook (applies to one application): open the application, go to Settings → Webhooks and click New Webhook
2
Enter the URL
Set URL to the full push URL of the Flashduty integration. Leave Secret Token empty: Flashduty authenticates with the
integration_key in the push URL and does not check the token.3
Select trigger events
Under Trigger Events, select Deployment Orders → Status Update. The other events (applications, environments, application orchestration, variable groups, changes, release stages) create no change even when selected, so you can leave them out.
How changes are merged
Status mapping
These deliveries return success and create no change:
- Events other than deployment orders: applications (App), environments (Env), application orchestration (AppOrchestration), variable groups (VariableGroup), changes (ChangeRequest) and release stages (ReleaseStageExecution). A change is a development workflow on a code branch and a release stage is a pipeline run state; neither is a deployment. A deployment started by a pipeline is recorded through its own deployment order
InvalidParameter with the state value in the message; later updates of that order are not affected.
Change content
Use labels for routing and for filtering the change list:
Environment names are read from the order’s jobs.
FAQ
Does a repeated delivery create a duplicate record?
Does a repeated delivery create a duplicate record?
No. A delivery with the same order, state and time is recorded once, and a late earlier state does not reopen an order that has already finished.
The push returns an InvalidParameter error?
The push returns an InvalidParameter error?
… is missingorinvalid …: the payload is incomplete or a field is malformed. Confirm it comes from an AppStack deployment order eventunsupported …orunknown …: Flashduty does not support this deployment order status yet. Contact us
Why are pipeline and code changes not recorded?
Why are pipeline and code changes not recorded?
Only deployment orders are recorded. Yunxiao pipelines (Flow) and code repositories (Codeup) have their own events, which this integration does not cover. An AppStack deploy step inside a pipeline creates a deployment order, which this integration records.
Why does a suspended order stay Processing?
Why does a suspended order stay Processing?
A suspended order has neither finished nor been withdrawn, so Flashduty keeps it in Processing until it succeeds, fails or is canceled.