Configuring DevOps Config
- UpdatedJan 30, 2025
- 2 minutes to read
- Yokohama
- DevOps
The DevOps engineer role installs and sets up DevOps Config, which is used to validate config data (committed by developers, or app engineers) before deployment.
Data validation configuration tasks | (Optional) Advanced configuration tasks to extend the use of the data model |
---|---|
Install DevOps Config application, content packs, and pipeline plugins.
|
N/A |
2. Create an application in DevOps Config. Create an application to set up the entity, and link between ServiceNow products. |
N/A |
3. Create a deployable in DevOps Config. Create a deployable to define the environments to deploy the configuration data for your application (typically Dev, Test, and Production). |
Extend the use of the data model by using components and collections for a deployable in DevOps Config. |
4. Upload your configuration data. Upload your configuration data from each tool source to DevOps Config by creating and running an import script. |
Upload configuration data depending on use case. |
5. Define policies in DevOps Config. Define policies to run for validation of config data using default DevOps Config policies. |
Administrate the full life cycle of PaCE policies and create your own. |
6. Map policies to a deployable. Map policies to a deployable to run for validation of config data. |
Extend the use of the data model by mapping policies to components and collections in DevOps Config. |
7. Define exporters in DevOps Config. Define exporters to export config data to your pipeline using default DevOps Config exporters. |
|
8. Configure your pipeline in DevOps Config. Configure your pipeline to interact with your data model. Use DevOps Config Azure DevOps pipeline tasks and Jenkins pipeline actions to integrate your pipeline with DevOps Config. |
N/A |
9. Run validation in DevOps Config. Run validation and review the results. |
N/A |