Access Cloud Manager environment variables into Docker

[mmarascu]

I’m trying to make some configurable docker keys from Cloud Manager Environment.

How can I pass environment configurations (secrets) from Cloud Manager to Docker file?

[Anmol_Bhardwaj]

You can download the environment variables as a JSON file from the API provided by adobe:

https://cloudmanager.adobe.io/api/program/{programId}/environment/{environmentId}/variables

After that, you can easily store them in Docker.

Reference: https://developer.adobe.com/experience-cloud/cloud-manager/reference/api/#operation/getEnvironmentVa... 

[miklosc53670490]

I think the question is more about how to NOT need to hardcode them in DockerFile. 
I don't want to hardcode them in the code and push them to the git repository. 

Can we access the above API from the docker instance that is created with the selenium tests in Cloud Manager? Without needing to place a "SECRET_KEY" inside the docker instance or anywhere in the code. It should come from the Cloud Manager configurations (environment) 

[mmarascu]

So what I need is to access those secret variables while running the ui.test docker container in Cloud Manager pipeline.

[Jörg_Hoh]

Can you please give some context what you mean with "Docker file"? Where in the context of Cloud Manager do you use a Docker file?

[mmarascu]

I will try to be more explicit, so I am not able to read the configured Cloud Manager environment variable  when doing the docker-compose up in the Custom UI testing step. I have tried different places to access them:

- in the pom.xml file of the ui.tests (ui-tests-docker-execution profile - docker compose - environmentVariables <VARIABLE_NAME>${env.VARIABLE_NAME}</VARIABLE_NAME>)

- in the docker compose yaml file as environment

- in the dockerfile as ENV

[Jörg_Hoh]

I am referring to the official documentation.

I understand it in a way, that it is the customer's responsibility to create the container; and that CM will startup the container. It's not that your maven build will start it up directly using some plugin or so.

For the environment variables it is stated "The following environment variables will be passed to your Docker image at run time."

That means that CM will inject these environment variables in your runtime, so that the code there can read them.

Now re-reading your post I assume that you want to run the same container for testing purposes on your local machine. Is this correct?

In that case you need to provide them as environment variables to your command (see the docker documentation, or the docs for docker compose). 

[mmarascu]

Following this official documentation, I should be able to set some secret environment variables in CM and access them at runtime by adding them in the pom.xml file (docker compose profile) under the existing ones.

Simulating this on local host by exporting these variables and then building and running the docker image would actually list them.

Trying the same in CM, would not list these already configured env vars that should be available at runtime in that pipeline. 

[Andres_Peréz]

Did you manage to fix it or any news in this? We're having a similar problem. Tried setting an env var via CLI commands unfortunately build profile is not pulling it.

[JosueZu]

Hey @mmarascu, have you managed to solve this issue? I'm facing pretty much the same issue right now.