AEM as a Cloud Service: Pipeline re-execution after environment variable changes
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article clarifies if and when pipeline re-execution is necessary after changing environment variables in Adobe Experience Manager as a Cloud Service.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all versions).
Symptoms
Questions arise regarding whether pipeline re-execution is required after updating environment variables when using Full Stack, Config, and Web Tier (Dispatcher) pipelines. This applies to all environments (dev, stage, prod) and to programs with a large number of environment variables. No specific error messages are reported.
Cause
Environment variable changes are applied at the runtime level in AEM as a Cloud Service. Most changes do not require pipeline re-execution, except when configuration files referencing those variables are deployed via the Config pipeline.
Resolution resolution
Follow the steps below to resolve the issue:
-
Identify the type of pipeline in use:
-
Full Stack Pipeline: If only environment variable values are changed (no code or OSGi config file changes), pipeline re-execution is not required. The new values are applied to the runtime environment after saving in Cloud Manager. If code or OSGi configuration files are changed, pipeline execution is required.
-
Config Pipeline: If YAML files deployed by the Config pipeline reference environment variables, re-execute the Config pipeline after updating environment variables to ensure new values are reflected in the deployed configuration. Environment variables are not deployed simultaneously with the Config pipeline; update variables before running the pipeline.
-
Web Tier (Dispatcher) Pipeline: If only environment variable values are changed (no dispatcher config file changes), pipeline re-execution is not required. If dispatcher configuration files are changed, pipeline execution is required.
-
-
The requirements above apply equally across all environments (dev, stage, prod).
-
Ensure that environment variables are correctly configured for the intended target service or environment before pipeline execution.