Moving Cloud Provisioning and Governance content across environments

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • You can move the content in the Cloud Provisioning and Governance application from one environment to the other. For example, develop an application in an environment and then move the application and all its dependencies to another environment for testing or production.

    Content entities that can be moved

    The Cloud Provisioning and Governance application consists of code, resources, content, and configurations.

    You can move the following content entities across environments:
    • Blueprints
    • Resource blocks
    • Cloud APIs

    Use the update sets to move the content entities. Update sets, which are XML files, group all the content into named sets and then moves these sets, as a unit, to other systems for testing or deployment. For information on how system update sets work, see System update sets .

    Content entity dependencies

    Each of the content entities has some direct dependencies that are automatically moved with the content to the new environment.

    The direct dependencies for each of these content entities are:
    Content entity Dependencies
    Blueprint
    • Resource blocks
    • Cloud APIs
    • MID scripts
    • Resource pools
    • Policies
    • Script includes
    • Cloud scripts
    Resource blocks
    • Resource pools
    • Resource operation policies
    • Script includes
    • Cloud APIs
    • Dependant resource blocks
    • MID scripts
    Cloud API MID scripts