adobe / adobe/aem-project-archetype

Cannot have different Pipeline variables for Stage & Prod - Cloud manager

Open
#1,120 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Groovy
Stars
596
Forks
432
Avg merge
10d 6h
Merged PRs (30d)
1

Description

Hi ,

The AIO_RUNTIME_NAMESPACE and AIO_RUNTIME_AUTH properties set in maven pom.xml files [1], when used from values configured in cloud manager[2], these are not getting picked-up during CI-CD process. When these variables are defined as pipelines variables values are picked-up during CI-CD process[3].

### Expected Behaviour
Pipeline variables should be unique for each environment when getting deployed.

### Actual Behaviour
Pipeline variables are the same for both Staging and Production environment.

### Reproduce Scenario (including but not limited to)
1. Configure Environment configuration variables in cloud manager
2. Run cloud pipeline to deploy to env.
3. Notice, SSR actions do not get deployed. Verify, using aio commands to see latest updated actions.
4. Configure pipeline configuration variables using aio commang line interface.
command:
5. Deploy the build using pipelines to the cloud env.
6. Verify the latest SSR actions are deployed.
command: wsk action get /\/\/\

#### Platform and Version
AEM Archetype Version 39
Node v14.21.1
NPM 6.14.17
Version - 2023.7.12874.20230726T072051Z-230702

![1](https://github.com/adobe/aem-project-archetype/assets/53895441/1c634cf0-d49f-4103-807e-df2d4324cb4b)
![2](https://github.com/adobe/aem-project-archetype/assets/53895441/8e73a456-a076-4465-8ac0-9c44d7747cd0)
![3](https://github.com/adobe/aem-project-archetype/assets/53895441/21b5d0fc-30c5-4f38-96d5-a864141badd8)

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the AIO_RUNTIME_NAMESPACE and AIO_RUNTIME_AUTH values in the maven pom.xml files and comparing Cloud Manager environment variables with pipeline variables. Reproduce the deployment for Staging and Production, then verify with the stated aio command that SSR actions are deployed with distinct environment values.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, nodejs
Domain
ci-cd, cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.