Hi,
I’m having troubles referencing dynamically created env variable from run command environment section.
I’ve found a few posts addressing this issue but neither of solutions provided there actually work and I thought it would be a good idea after all to sum it up in one single post here.
Below is an example of what I’m trying to archive.
environment: runs before any commands, so the envs are not going to exist when you run ./script.py read_env_variables_here
It would better to put them in the UI, is there a reason you are trying to do it this way? There may be examples of being able to do it this way on the forums, I would need to look.
That would be a dynamically calculated variable so no way we can pass it via UI.
Just to make sure cause I skipped that part echo $FOO_ENV_VAR is ready the property just fine.
So as a workaround we can pass it as a script parameter but syntax wise yaml reads easier when it is in the list under environment: