DevOps Config reference

DevOps Config reference content.

Important:

Starting with the Washington D.C. release, DevOps Config is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.

• Update the associations for a deployable
  Update the name and description of a deployable as well as its associations with applications and other items. This procedure is optional.
• Types of configuration data supported by DevOps Config
  DevOps Config stores configuration data of every layer of the IT stack in a centralized location.
• CDM data model
  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.
• APIs and DevOps Config
  You can use DevOps Config and CDM APIs to access your config data.
• DevOps Config roles
  DevOps Config uses these roles.
• How encrypted data is handled
  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.
• Domain separation and DevOps Config
  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.
• Default DevOps Config policies
  The DevOps Config Policy content pack contains a set of default DevOps Config policies to validate your configuration data.
• Default DevOps Config exporters
  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.