Argo CD integration with DevOps Change Velocity
- UpdatedAug 1, 2024
- 3 minutes to read
- Washington DC
- DevOps
The Washington DC release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.
Connect to your Argo CD instance to automate the deployment of applications from GitHub repositories.
Argo CD integration overview
This integration enables the ServiceNow platform to manage the change request closure process based on the sync status received from Argo CD for continuous deployment of applications.
You must activate the DevOps Integration with Argo CD plugin (sn_devops_argocd) before connecting your Argo CD instance in ServiceNow. For more information on activating a plugin, see Activate a plugin.
Workflow
Here is the workflow of how the continuous deployment process works through Argo CD in ServiceNow DevOps.
- Create an Argo CD tool connection in ServiceNow DevOps Change Velocity using the Classic or Workspace UI.
- Create a webhook in Argo CD manually.
- Update your Config file in the GitHub repository for deployment. While updating the Config file, specify the change request number in the commit tag (sn_devops_change-<change request number>).Note: The change request number specified in the commit tag must already be created by the CI pipeline and in the implement state.
- Sync the required app associated with your Config file and repository in Argo CD.
- Once sync is successful, notifications are sent to ServiceNow DevOps and inbound events are created.
- Change request number is retrieved from the inbound events and updated with the Argo CD synchronization status.
- Change request is closed and based on the sync status, the close code, worknotes, and close notes fields are updated in the change request.
Example
The following examples specify how changes made in Argo CD are notified to ServiceNow DevOps through the webhook.
- The Config file is updated in GitHub with the following commit tag format:
- Inbound events are created in ServiceNow when an app is synced in Argo CD:
- If sync is successful, the change request is closed and the close code, worknotes, and close notes fields are updated in the change request:
