Combined DevOps Config release notes for upgrades from Vancouver to Yokohama

How to use this page

To help you prepare for your upgrade, we have combined the cross-family DevOps Config release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Vancouver to Yokohama.

Tip:

If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

Important information for upgrading DevOps Config to Yokohama

Before you upgrade to Yokohama, review these pre- and post-upgrade tasks and complete the tasks as needed.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

New features

Between your current release family and Yokohama, new features were introduced for DevOps Config.


Release	Release notes
Vancouver	Combined Jenkins upload action added Use the snDevOpsConfig Jenkins combined action to upload your config data, get snapshots, and register your pipeline in the place of three separate Jenkins actions. Kubernetes policies added to DevOps Config Policy content pack Use the advanced policies added to the DevOps Config Policy content pack to validate your Kubernetes configuration. Red Hat OpenShift policies added to DevOps Config Policy content pack Use the advanced policies added to the DevOps Config Policy content pack to validate your Red Hat OpenShift configuration. [Placeholder link text to key bundle-devops.pace-create-policy-template] Create PaCE policy templates for policies and policy versions that you use frequently. [Placeholder link text to key bundle-devops.pace-policy-mapping] Use Static and Dynamic mapping to map multiple policies against a single deployable or multiple deployables. [Placeholder link text to key bundle-devops.cdm-manage-file-config-data-file-node] Add and manage files to the config data of a CDM application or a shared component using file nodes. You can also include these file nodes under a component to collections and deployables. You can manually validate these files and then publish the snapshot. When exporting for deployment, the valid config data includes these file nodes. Use any UTF-8 character for naming nodes You can define a node using any UTF-8 character, including the forward slash (/). In the CDM REST API, you can provide the name path in array formats that can include any UTF-8 character. Upload XML files keeping XML attributes intact Upload your config data stored in XML format to CDM apps. The CDM XML Parser support custom header and delimiter attributes to parse CSV format into JSON format in a way that makes them easily recognizable. You can also export config data from the CDM app to CSV format, keeping attributes and enclosing text in their original format. The ignoreAttributes argument is added in the CDM REST APIs for uploading config data to skip processing of attributes from XML files. Import your config data from CSV files Import your config data into CDM apps by uploading a CSV file. The CDM CSV Parser converts attributes and data in CSV format into JSON format in a way that makes them easily recognizable. You can also export config data from the CDM app to CSV format, keeping attributes in their original format. The dataFormatAttributes argument is added in the CDM REST APIs for uploading config data to configure attributes during CSV upload. Map policies to deployables in DevOps Config using dynamic mapping Define business conditions and map policies to multiple deployables dynamically based on business conditions. Validation is triggered on dynamically mapped policies at run time based on the latest conditions matching the deployables.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Changes

Between your current release family and Yokohama, some changes were made to existing DevOps Config features.


Release	Release notes
Vancouver	Support the return of node data Added the includeNodeInOutput argument to the returnDataforNodeName-now exporter to return the node data after excluding the node name.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Removed

Between your current release family and Yokohama, some DevOps Config features or functionality were removed.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Deprecations

Between your current release family and Yokohama, some DevOps Config features or functionality were deprecated.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Activation information

Review information on how to activate DevOps Config.


Release	Release notes
Vancouver	Install DevOps Config by requesting it from the ServiceNow Store. Visit the ServiceNow Store website 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.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Additional requirements

If any additional requirements were introduced or changed for DevOps Config we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Browser requirements

If any specific browser requirements were introduced or changed for DevOps Config we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Accessibility information

Review details on accessibility information for DevOps Config, such as specific requirements or compliance levels.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Localization information

If there are specific localization considerations for DevOps Config we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Highlight information

If there are specific highlight considerations for DevOps Config we have noted them here.


Release	Release notes
Vancouver	Added the Jenkins action that combines three tasks in one action. Added advanced default policies to validate your snapshot. Added support for adding files to the config data of CDM applications and shared components. Added support for UTF-8 characters for the node names. Added support for uploading and exporting config data to and from CDM in XML and CSV formats. Dynamically map policies to deployables based on business conditions. See [Placeholder link text to key bundle-devops.devops-config-landing-page] for more information.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.