Devops Family

You use the CdmPolicyUtil script include to add warning and failure messages to validation results in the CDM Policy Validation Results table. CDM expects validation warnings and failures to contain a node path, a snapshot ID, and a reference to the impacted node.

Submit a request for a component in an application that could be reused across multiple applications to be added to a shared component library.

Create an application as the container for all config data for a service (an application service, application model, or dynamic CI group [infrastructure] in the CMDB).

Generate a new service (an application service, application model, or dynamic CI group [infrastructure application type]) in the CMDB) and create a CDM application as the container for the config data for the service.

Delete a CDM application to delete all associated config data and snapshots.

Use the Config Data Analyzer tool to find similarities and differences between the config data of two applications. You can compare either different applications or different changesets of a particular application.

Use the Config Data Analyzer tool to find similarities and differences between any two committed changesets from the same or different applications.

Descriptions and examples of differences between CDM applications when using the Config Data Analyzer tool.

Use the Config Data Analyzer tool to find changes between two snapshots of a deployable of an application.

Use the Config Data Analyzer tool to find similarities and differences between two snapshots from the same or different applications.

Export a snapshot to generate config data for the pipeline to use.

Service delivery can include multiple teams working at the same time on config data with potentially hundreds of configuration changes every day. Because changes can be in conflict with earlier changes by a different user, CDM manages commits and snapshots to block commits that conflict. You are notified of changeset conflicts to help you to resolve them.

Update config data in an existing changeset or in a new changeset. You can save your changes for later updates or save and commit the changes. Committing the changes generates a snapshot for each deployable that is affected by the changes.

Select the changeset on the Activity tab and then select Delete.

View the details of changes in each committed changeset on the Activities tab.

A changeset is a draft copy of an application that you can update and save as often as needed. When you are satisfied with your changes, you can commit the changeset to apply the changes to the application. Committing

Define or update a collection while working in a changeset of a application.

Activate a component library to make all of its shared components available for use.

Add or update a shared component in a component library.

Create a component library to manage components that can be reused across multiple applications.

Delete a component library and all of its components if no application is using the library's components.

Review a request for adding a component to a component library and approve or reject it.

Define or update a component while working in a changeset.

Some applications may share the same basic structure and require nearly identical configuration data. Shared components in CDM enables you to use a component across several applications. For better organization, these shared components are managed in component libraries.

Publish a version of a shared component in a library so that it can be used in an application.

Contextual variables are out-of-the-box variables delivered by ServiceNow that enable you to use the context of a node to define a variable.

A high percentage of alerts occur due to errors in config data. If the chain of events that resulted in an alert includes a change request that involves the same CI as the alert, then you can use a variety of tools to isolate the config changes that might have caused the alert.

The CDM data model is a standardized data structure that supports the broader life cycle of software delivery — automation, quality validation, and CSDM. CDM imports existing config data, validates it using policies that you define, and exports valid config data to your organization's existing DevOps pipeline to implement applications, services, and infrastructure.

Add the data structure to a new application that will accept the uploaded config data into appropriate nodes.

Create a deployable while working in a changeset. You can add multiple components and collections to a deployable.

Delete a deployable to delete its config data and all associated snapshots.

Map policies to a deployable to define the validation processes that the config data must pass. You can map policies to a deployable using static mapping or dynamic mapping.

Update the name and description of a deployable as well as its associations with applications and other items. This procedure is optional.

You can update the config data of an application by creating or opening a changeset on the Config data tab, where you update the structure and CDIs of the config data.

View the execution record to analyze policy execution.

Change the default deletion period. By default, records of exporter executions are deleted after a period of three years.

Archive an exporter to preserve its record and remove it from the lists that you use in your everyday work.

Copy an existing exporter script as a starting point for a custom exporter.

Delete an exporter to ensure that users cannot use it to generate config data.

View a list of exporter executions to identify config updates that are successful and to isolate changes that caused failure in the pipeline.

Generate sample code of an API invocation for an exporter. The code can invoke the exporter. Select from several commonly used languages.

Set and validate input settings to test an exporter before you export the config data in a snapshot.

Add and manage files using file nodes in the config data model of a CDM app or in a component library.

The CDM CSV parser enables parsing of data in CSV files, so when you upload config data from a Comma-Separated Values (CSV) file into CDM, you can easily identify the data format attributes and config data in the CDM editor or list view.

The CDM XML parser enables the parsing of attribute key-value pairs in XML files, so when you upload config data from an XML file into CDM, you can easily identify the attributes of each element in the CDM editor or list view.

An application in CDM is the full collection of config data for an application service, application model, or dynamic CI group [infrastructure] in the CMDB. After you upload your source config data, the application can support all potential deployables that make up each version of the development, test, and production environments of the service.

List of roles and permissions in CDM.

By default, encrypted values appear in all views as *******. Only users with the CDM Secrets [sn_cdm.cdm_secrets] role can view, create, update, and delete encrypted values in config data. The system validates and exports encrypted data appropriately.

Add a shared component to an application, view shared components that are available to add, or remove a shared component from an application.

Publish a snapshot so that it can be exported to enable the CI/CD pipeline to access and use the config data. Exporters can execute only on published snapshots.

Validate a snapshot from the Snapshot tab. For example, manually validate a snapshot to ensure that its valid for new policy requirements.

View the snapshots of all deployables for an application on the Details tab for the application. The release pipeline can access only a snapshot that is the currently published version.

CDM system properties.

You first create a new CDM application structure and then upload the existing config data into the structure.

For every change to an environment, there may be tens or hundreds of rules (policies) that need to be checked. CDM enables you to auto-validate configuration data to ensure that configuration changes are error-free and policy-compliant before the config data is consumed.

When a policy that executes against a deployable snapshot fails or generates an error or warning, the policy identifies the offending CDI and the reason for the failure. While working in a changeset, you can use the Validation failures panel to navigate directly to the offending CDI so you can correct the issue.

View validation failures and warnings on the Validation results tab for the snapshot.

Define variables and set their values in components, collections, and deployables.

The unified view of component libraries in the DevOps Config Workspace provides a single location to view and manage component libraries and the components within them.

DevOps Config stores configuration data of every layer of the IT stack in a centralized location.

Create an app in DevOps Config to manage its configuration data, and link DevOps Config with other ServiceNow products, including DevOps Change Velocity.

When you create an app in DevOps Config, not only is it the container for the config data of the application, but the application model you choose links DevOps Config with other ServiceNow products, including DevOps Change Velocity.

Use these tasks in your Azure DevOps pipeline to interact with the DevOps Config data model.

DevOps Config uses Configuration Data Management and Policy as Code Engine platform capabilities to manage configuration data and policies.

You can use DevOps Config and CDM APIs to access your config data.

The DevOps Config Exporter content pack contains a set of default DevOps Config exporters of data that can be used as input for further deployment and provisioning activities.

The DevOps Config Policy content pack contains a set of default DevOps Config policies to validate your configuration data.

Define exporters in DevOps Config to export config data from all or part of the data model as input for further deployment or provisioning activities.

Define policies in DevOps Config to validate your configuration data.

DevOps Change Velocity collects data from all of your DevOps tools, providing visibility across the entire lifecycle of deployment, while DevOps Config manages and validates your DevOps configuration data.

Domain separation is unsupported for DevOps Config. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

By default, the DevOps Config Policy content pack contains a set of generic policies to validate your configuration data.

Use DevOps Config to store and manage all of your config data as a single source of truth. You can also use DevOps Config to validate your config data before deployment, and resolve conflicts in deployed config data.

Use these actions in your GitHub pipeline to interact with the DevOps Config data model.

Use the DevOps Config Insights dashboard with Performance Analytics to quickly identify configuration errors and take action. View snapshot validation trend, open changesets, and failed snaphots for all applications and deployables.

Install DevOps Config Exporter content pack for a default set of DevOps Config exporters that you can use as-is, or customize for your needs.

Install DevOps Config Policy content pack for a default set of DevOps Config policies that you can use as-is, or customize for your needs.

Integrate your Argo CD, Azure DevOps, or Jenkins pipeline with DevOps Config to interact with your data model.

Use these actions in your Jenkins pipeline to interact with the DevOps Config data model.

By default, the DevOps Config Policy content pack contains a set of policies to validate your Kubernetes configuration.

The ServiceNow DevOps Config application validates and manages the configuration data of your enterprise applications across every stage of the DevOps pipeline.

Mapping a policy to a deployable enables you to validate updates on it. These policies in DevOps Config are powered by Policy as Code Engine (PaCE).

By default, the DevOps Config Policy content pack contains a set of policies to validate your Red Hat OpenShift configuration.

DevOps Config reference content.

DevOps Config uses these roles.

After you have installed and configured DevOps Config, validate the configuration and review the results.

Configure your Argo CD, Azure DevOps, or Jenkins pipeline with DevOps Config to interact with your data model.

These are some of the common DevOps Config terms.

The developer, or app engineer, role uses DevOps Config, once it's installed and set up by the DevOps engineer role, to validate and correct config data (that they commit) before it gets deployed.

Domain separation is supported for CDM. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

Install the DevOps Config application from ServiceNow Store applications. Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

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.