--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Support for continuous delivery (configuration management) # Support for continuous delivery (configuration management) {#ariaid-title1} * Release version: Yokohama * * Updated August 11, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Support for continuous delivery (configuration management) The Cloud Provisioning and Governance application in ServiceNow Yokohama release supports integration with continuous delivery solutions, specifically configuration management providers like Ansible (the default). This integration enables automated deployment and configuration of entities such as applications and servers through application profiles or resource blocks. It also supports post-provisioning actions to enhance VM deployment workflows. Show full answer Show less ## Key Features * **Application Profile Based Approach:** Create multiple application profiles (e.g., PostgreSQL, Apache) mapped to configuration management providers. Selecting a profile in the order catalog presents a configuration grid with provider-specific attributes for customization before provisioning. * **Resource Block Based Approach:** Use resource blocks (e.g., Apache2) within blueprints to represent managed entities. The same block can support multiple instances. Selecting a provider type in the order catalog displays relevant configuration attributes, which can be saved post-provisioning to the CMDB for reuse. * **Post-Provisioning Actions:** Invoke Ansible jobs as post-provisioning (day-2) operations after VM deployment to execute configuration tasks automatically. * **Blueprints:** Blueprints include operations like BootstrapNode, Register Node, and ExecuteConfigPackages, which automate provisioning and configuration steps. Note that from Orlando release onwards, new blueprints cannot be created on upgraded instances, but existing ones continue to function. ## Practical Steps for Implementation 1. **Create Credentials:** Set up credentials for Ansible Tower to allow Cloud Provisioning and Governance to access the configuration management provider securely. 2. **Configure Provider:** Create the workload provider type and provider instance in the system, then run discovery to identify existing resources managed by the provider. 3. **Create Application Profile:** Define application profiles based on discovered inventories to represent the applications managed by the configuration management provider. 4. **Create Blueprint:** Build blueprints incorporating necessary operations and customizable input parameters such as application profiles and credentials. 5. **Provision Resource:** Deploy the resource via the Cloud User Portal, monitoring stack status for provisioning steps including bootstrapping, registration, and configuration execution. ## What This Enables for ServiceNow Customers ServiceNow customers can automate and standardize application and infrastructure deployments by integrating with configuration management tools like Ansible. This facilitates consistent environment setup, reduces manual configuration errors, and supports ongoing configuration through post-provisioning jobs. The dual approach using application profiles or resource blocks offers flexibility to manage resources at different abstraction levels. Storing configuration data in the CMDB enhances visibility and governance over deployed infrastructure. The Cloud Provisioning and Governance application supports integration with continuous delivery solutions (also known as configuration management). Ansible is supported as the default config management provider. The Cloud Provisioning and Governance application supports configuration management providers in two ways: * Application profile based approach: Create an application profile for an entity and in the order catalog form, select that profile to deploy that entity. Each profile has a config installable. You can create multiple application profiles- as an example, one for PostgreSQL and one for Apache. Each profile can be mapped to a configuration management provider. In the Cloud User Portal, based on the profile you select, a configuration grid appears populated with attributes and values for that specific configuration management provider. You can modify any values in the order form and provision the entity. * Resource block based approach: Use a resource block, like Apache2, in a blueprint to represent an entity that a configuration management provider manages. The same resource block can be used to support more than one entity of the same kind. As an example, an Apache2 resource block can be used to support multiple Apache2 servers. In the order catalog form, select a provider type and then select a provider. Based on the specific provider, configuration management attributes and values appear. Once you provision the entity, you can save the configuration of the resource block and store it in the CMDB for future use. * Post-provisioning actions during catalog deployment: Users can call ansible job as a post-provisioning step in any catalog which deploys a VM. This will be executed as a day-2 operation once the VM installation is completed. For more information on the processes, see and . {#support-config-management-providers__ul_qys_vtg_lbb} Important: Starting with the Orlando release, the cloud provisioning blueprints are available on instances upgraded from a previous release but you cannot create new blueprints. Existing blueprints and catalog items from those blueprints remain unaffected and continue to work. ## What to do {#support-config-management-providers__section_qnz_lhh_sz} {#support-config-management-providers__table_myg_bq3_lfb__entry__3} | Step | Goal | See these topics | |-|-|-| | 1. Create credentials for Ansible. | Enable Cloud Provisioning and Governance to access the configuration provider with the necessary credentials. | [Configure Ansible Tower user name and password](https://servicenow-prod.fluidtopics.net/dRnl1KVj2wGouEgQi~tjjQ "Configure Ansible Tower credentials to access the Ansible Automation Engine through your instance.") | | 2. Create the workload provider type, and then create the provider. | Configure Cloud Provisioning and Governance to work with the configuration management provider of your choice. Then run discovery on the provider, using the credentials you provide, to find the resources that the provider already owns. | [Create a workload provider type](https://servicenow-prod.fluidtopics.net/4iWfuOuaec1wPZQle0GfSA "Create a workload provider type for each new configuration management provider. This information appears in the order catalog form as management attributes that your users can select when provisioning a virtual resource through a configuration management provider.") and [Create an Ansible configuration management provider and run Discovery](https://servicenow-prod.fluidtopics.net/HsHKXhJIEE8fJdgYIPpgqg "Create an Ansible configuration management provider, and then run Discovery on the provider to find its resources.") | | 3. Create an application profile with a mapping | Create the profile that defines the application that the configuration management provider manages. The profile is based on the discovered inventories in the provider. | [Create an application profile](https://servicenow-prod.fluidtopics.net/26Jd8TTAl0fM~m6ZOkS0fQ "An application profile specifies application software to install on newly-provisioned resources. Users can select applications when they request a stack. Use application profiles when you integrate with configuration management (continuous delivery) providers such as Ansible playbooks.") | | 4. Create a blueprint | Create a blueprint with BootstrapNode, Register Node, and ExecuteConfigPackages operations on the virtual resource that the configuration provider manages. You can also customize the input parameters on the form to allow the user to select important inputs, like the application profile template, organization, and credential ID. | | | 5. Provision a resource from the Cloud User Portal | The resource should provision, with the stack status indicating the BootstrapNode, Register Node, and ExecuteConfigPackages steps. | | [ ] {#support-config-management-providers__table_myg_bq3_lfb}