--- title: Configuring and running a promotion (early access) description: Promote PingOne resources from a source environment to a target environment using the Promotions page. component: pingone page_id: pingone:early-access-features:ea-p1_configure_promotion canonical_url: https://docs.pingidentity.com/pingone/early-access-features/ea-p1_configure_promotion.html revdate: December 1, 2025 section_ids: before-you-begin: Before you begin steps: Steps result: Result verify-the-promotion: Verify the promotion steps-2: Steps --- # Configuring and running a promotion (early access) Configure and run a promotion to move PingOne configuration resources from a source environment to a target environment. ## Before you begin * You must have at least two environments in your organization, and both environments should include the same PingOne services: * Source environment This environment contains resources you want to promote to another environment. * Target environment This is the environment to which you are promoting resources from a source environment. * You must have the Promotion Admin role or a custom role with equivalent permissions in both environments. * Ensure that promotion variables were created for resources that require them. Learn more in [Promotion variables (early access)](ea-p1_promotion_variables.html). * Review the [promotion retention policies](ea-p1_promote.html#p1-promotion-retention). ## Steps 1. In the PingOne admin console for your source environment, go to **Promote > Promotions**. 2. Click **Run a Promotion**. If you haven't configured a target environment for your promotions from this source environment, you're prompted to select one. If you've already configured a target environment, you're prompted to confirm that the target environment listed is correct. | | | | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | To change the target environment, cancel out of the modal and go to **Settings > Environment Properties**. Select a different environment from the **Target Environment** field in the **Configuration Management** section of the **Environment Properties** page. Then return to **Promotion Variables** and start the variable creation process again. | After you confirm the target environment, PingOne takes snapshots of both environments, compares configuration resources, and lists the resources that you can promote. ![A screenshot of the Select Resources to Promote page without anything selected.](_images/p1-promote-select-resources.png) 3. On the **Select Resources to Promote** page, search for and select the resources you want to promote. | | | | - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | * If a **View Warnings** button appears, click it to review any potential issues that might affect the promotion, such as broken references. Cancel the promotion, address any issues that relate to the resources you want to promote, then restart the promotion. ![A screenshot of the View Warnings button on the Select Resources to Promote page.](_images/p1-promote-view-warnings.png) * You can promote up to 100 configuration resources in a single promotion. Dependencies that are automatically included with the selected resource don't count toward this limit. * You should promote small, easily testable sets of resources to simplify testing and troubleshooting. | 4. Click **Next**. 5. On the **Map Resources** page, map the resource to an existing resource in the target environment or add it as a new resource. This page displays only if you haven't promoted a particular resource to the target environment before. After the resource is promoted, the promotion service recognizes that the resource exists in both environments and remembers the mapping for future promotions. * **Map** to an existing resource in the target environment If the promotion service finds a resource in the target environment that might match the resource you want to promote, the **Map** toggle is set to on (blue) and the matching resource is selected in the **Target** list. When you run the promotion, the version from the source environment overwrites the version in the target environment. ![A screen capture of the Map Resources modal with a matching resource in the Target field.](_images/p1-promote-map-to-existing-resource.png) If you don't want to map the resource as the configuration service suggests, select a different resource in the **Target** list, or click the **Map** toggle to off (gray) to create the resource as new in the target environment. * **Promote as New Resource** If the promotion service doesn't find a clear match in the target environment for the resource, the **Map** toggle is off by default. This means that when you run the promotion, the resource is created as new in the target environment. You can also choose to map the resource manually by clicking the **Map** toggle to on (blue) and selecting a resource from the **Target** list. ![A screen capture of the Map Resources modal with My First App in the Source field.](_images/p1-promote-map-resources.png) 6. Click **Confirm and Continue**. If the resource includes dependencies, the **Auto-Selected Dependencies** modal opens. If a configuration resource is required by the parent resource and the promotion service doesn't find a matching resource in the target environment, you must also promote that resource. If a configuration resource has a dependency for which a corresponding or matching resource already exists in the target environment, you can choose not to promote the dependency. 7. Select to map or create the listed dependencies and click **Continue**. 8. On the **Confirm Promotion** page, review the promotion summary and add release notes. 9. Click **Run Promotion** | | | | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | Run the promotion soon after completing the promotion configuration to ensure that you are capturing the most up-to-date configuration in the source environment. The promotion can become stale if significant configuration changes are made in the source environment between the time that you configure the promotion and when you run it. | ### Result You're returned to the **Promotions** page and the current promotion is listed with a status of **In Progress**. After a few seconds, refresh the page. | | | | - | ---------------------------------------------------------------------------------------------------------------------------------------- | | | Most promotions will complete within 30 seconds. This time can vary based on the size and number of resources included in the promotion. | The status will change to **Success** for a successful promotion. | | | | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | If the status changes to **Failed**, click the **More Options** icon (⋮) and select **View**. Some resources might have been promoted successfully while others failed. Review the details to determine which resources were affected and troubleshoot any issues, then run the promotion again. You can also rollback a promotion to revert the changes made by a promotion that completed with some errors. Learn more in [Rolling back a promotion (early access)](ea-p1_promotion_rolling_back.html). | ## Verify the promotion To verify the results of the promotion, first confirm the details of the promotion in the source environment. Then check the target environment and ensure that it matches what you expect. ### Steps 1. In the PingOne admin console for your source environment, go to **Promote > Promotions**. 2. Locate the promotion in the list, click the **More Options** icon (⋮), and select **View**. * Overview tab The **Overview** tab shows information about when the promotion was started and completed, the source and target environments, the status of the promotion, and any release notes that were added. ![A screenshot of the Overview tab for the initial promotion of My First App.](_images/p1-promote-promotion-complete-overview-tab-myfirstapp.png) * Promoted Resources tab The **Promoted Resources** tab shows the details about the resources that were promoted. ![A screenshot of the Promoted Resources tab for the initial promotion of My First App.](_images/p1-promote-promotion-complete-promoted-resources-tab.png) 3. On the **Overview** tab, click **View Target Environment**. You're taken to the admin console for the target environment so that you can confirm that the promoted resources exist and match what you expect.