AEM Cloud Manager: Stage environment not available for config-only non-production pipelines
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article describes why the Stage environment is not available when creating a non-production pipeline for configuration changes in Adobe Experience Manager Cloud Manager, and provides guidance on how to deploy configuration changes to Stage.
Description description
Environment
- Adobe Experience Manager (AEM) as a Cloud Service (all versions)
Symptoms
When creating a non-production pipeline in Cloud Manager for deploying /config changes, the Stage environment does not appear as an option in the environment selector, even though the Stage environment is present and in a Ready state. No error messages are displayed, but the expected Stage environment cannot be selected for this pipeline type.
Steps to reproduce
- Open AEM Cloud Manager.
- Click Add a pipeline and select non-production pipeline.
- Configure the pipeline for Targeted deployment → Config.
- Attempt to select an environment; Stage is not available.
Cause
The Stage environment is not selectable for non-production pipelines due to Cloud Manager design. Config-only pipelines are limited to Development environments unless run as a Production pipeline, which follows the Stage → Production flow.
Resolution resolution
Follow the steps below to deploy configuration changes to the Stage environment:
- In Cloud Manager, go to Pipelines and select Add Pipeline, then Add Production Pipeline.
- Select Targeted deployment, then choose Config under Include.
- Specify the repository, Git branch, and set Code Location to
/config(or the relevant path). - Enable Pause before deploying to Production to validate changes on Stage before proceeding to Production.
- Run the pipeline. After validation on Stage, you may choose not to approve the Production step if you wish to keep changes only on Stage.
If a Stage-only pipeline is required for broader application changes (code and config), use a Full Stack Code pipeline. Note that this will deploy the entire application, not just /config.