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)
Configure Environment configuration variables in cloud manager
Run cloud pipeline to deploy to env.
Notice, SSR actions do not get deployed. Verify, using aio commands to see latest updated actions.
Configure pipeline configuration variables using aio commang line interface.
command:
Deploy the build using pipelines to the cloud env.
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
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)
Platform and Version
AEM Archetype Version 39 Node v14.21.1 NPM 6.14.17 Version - 2023.7.12874.20230726T072051Z-230702