I’m promoting a build to a different environment that triggers a new pipeline (inside the same .drone.yaml file). I’m specifying a key and value in the parameter but can’t access them during the deployment.
I was under the impression that parameters would be passed in as environment variables but when printing all env vars as one of the commands it doesn’t show. Is my understanding correct or is this not how parameters work?
The easiest way to test that environment variables are being automatically injected into your pipeline is to run the env command which will demonstrate the parameter was properly added, as show in this example:
So, in that case, what was the solution?
I’m trying to create key/value like APP_STEP=CHECK but it never appears in the “env” command inside the pipeline. Can’t find more documentation than two or three links…