Stage: post-deploy

The post-deploy stage closes the loop on the change workflow. After a successful deploy, the ServiceNow change requests are moved to Implemented then Closed, so the change lifecycle is complete and reportable rather than left hanging.

Part of the Full pipeline action map. Use the Fullscreen button on the diagram to view it edge-to-edge.

flowchart TD
  DEPLOY["Successful deploy<br/>(dev / qa / prod)"]
  CD["servicenow:cr:close:dev"]
  CQ["servicenow:cr:close:qa"]
  CP["servicenow:cr:close:prod"]
  SDB[("ServiceNow CR<br/>Implemented -> Closed")]

  DEPLOY --> CD
  DEPLOY --> CQ
  DEPLOY --> CP
  CD -.-> SDB
  CQ -.-> SDB
  CP -.-> SDB

  class CD,CQ,CP post
  class SDB snow
  class DEPLOY io
  classDef post fill:#1f8f6b,stroke:#0d5a42,color:#ffffff
  classDef snow fill:#d29922,stroke:#8a6500,color:#ffffff
  classDef io fill:#57606a,stroke:#32383f,color:#ffffff

Jobs in this stage

Job	What it does	Why
`servicenow:cr:close:dev`	Moves the dev change request to `Implemented` then `Closed` via the ServiceNow API.	A change record that never closes is noise; closing it makes ServiceNow reflect reality.
`servicenow:cr:close:qa`	Closes the qa change request after a successful qa deploy.	Completes the qa change lifecycle.
`servicenow:cr:close:prod`	Closes the prod change request after a successful prod deploy; updates the CMDB with the new image digest + Evidence Vault / Fides trail link.	Completes the production change lifecycle and keeps the CMDB current.

All three are allow_failure: true — a ServiceNow outage at close-time never fails an otherwise-successful deploy; the close can be retried.

Why this stage exists

The compliance story is only complete when the change record is closed. This stage turns “we deployed” into “the documented change is implemented and closed,” which is exactly what an auditor expects to see end-to-end.

Stages: deploy-prod → post-deploy → gitops · all stages