--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia 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: Australia Updated November 5, 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 supports integration with continuous delivery solutions, also known as configuration management. Ansible is the default supported configuration management provider. Note that starting with the Brazil release, Cloud Config Management is being prepared for future deprecation---it will be hidden and no longer installed on new instances but will continue to be supported for existing deployments. Show full answer Show less This support enables you to automate and manage configurations in your cloud environments effectively, leveraging configuration management providers during provisioning and post-provisioning steps. ## Key Features * **Application profile based approach:** Create application profiles representing entities (e.g., PostgreSQL, Apache) and map them to configuration management providers. When selecting a profile in the order catalog, a configuration grid appears with provider-specific attributes and values that can be modified before provisioning. * **Resource block based approach:** Use resource blocks in blueprints to represent entities managed by a configuration management provider. This method supports multiple entities of the same type using the same resource block. Configuration attributes appear in the order form based on the selected provider, and configurations can be saved in the CMDB for reuse. * **Post-provisioning actions:** Ansible jobs can be executed as post-provisioning steps (day-2 operations) after VM deployment completes, allowing further configuration automation. * **Blueprint availability:** From the Orlando release onward, existing cloud provisioning blueprints remain functional after upgrades, but creation of new blueprints is restricted. ## Practical Steps for Customers 1. **Create Ansible credentials:** Configure Ansible Tower username and password to enable secure access. 2. **Set up the workload provider:** Create the workload provider type and provider in Cloud Provisioning and Governance, then run discovery to import existing resources from the configuration management provider. 3. **Create an application profile:** Define the applications managed by the configuration provider based on discovered inventories. 4. **Create a blueprint:** Build blueprints incorporating BootstrapNode, Register Node, and ExecuteConfigPackages operations to automate provisioning steps. Customize input parameters to capture key user inputs. 5. **Provision resources:** Use the Cloud User Portal to provision resources, observing stack statuses that reflect configuration management steps. ## Why This Matters This integration simplifies the deployment and management of cloud resources by embedding configuration management directly into the provisioning lifecycle. It enables consistent, automated configuration of applications and infrastructure, reduces manual errors, and supports day-2 operations to maintain desired states post-deployment. 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. Important: Starting with the Brazil release, Cloud Config Management is being prepared for future deprecation. It will be hidden and no longer installed on new instances but will continue to be supported. For details, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base. 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://www.servicenow.com/docs/FbTW_eA72u0utyPSxUBzig "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://www.servicenow.com/docs/zG4vPqgs0wMZOrpcemSFXQ "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://www.servicenow.com/docs/_B_RW9p5ddMiI~IkNaJ2Pw "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://www.servicenow.com/docs/XtnCJJtjlxwXAXyoqd9Drw "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}