Global parameters config/stage file

[mstrakow]

During deployment I was trying to replacing all global variables environment-related. I'm using one .json config file for all env.
It looks like below :

what I'm getting during process is :

any clue how to properly configure .json file format to be able to replace global variables ?
Thanks in advance for any hint.

[NowinskiK]

List all env variables available for the agent to make sure you use the correct names.
You shouldn't use - in variable names - use _ instead.
In pipelines, you can reference predefined variables as environment variables.
For example, the variable Build.ArtifactStagingDirectory becomes the variable BUILD_ARTIFACTSTAGINGDIRECTORY.
https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml

[mstrakow]

Thank You for Your feedback Kamil.
I don't think this is a main cause of what is happening.
I've created same configuration file but in .csv with the same naming convention of env. variables

and it throws

PROJECT-NAME is a variable that I'm passing as pipeline parameter and I see this variable in env.

Process is not complaining about 3 previous variables that are in config file DBX-DOMAIN,DBX-ID,DBX-CLUSTER-ID,
which are also visible on env. variables.

When I switch to .json config file I still get error like in my 1st comment, but maybe this is because whole .json is checked at once and if one of env. is missing is giving ##[error]Invalid JSON primitive: .
I don't know this make sense.

[NowinskiK]

Did you try:

1. having only one item in config file, then
2. replace variable name from PROJECT-NAME to PROJECT_NAME?

How do you think why Microsoft does NOT use dashes in environment names?
Well, if you don't want to follow my suggestions then carry on trial & error...

[mstrakow]

Thanks Kamil for Your response.
You right that "-" are not supported by Azure, but "-" is not replaced by default to "_", that I was confused. But anyway, I removed all "-" from my variables and with .csv param file it worked as expected.
But not with .json it's still :
##[error]Invalid JSON primitive: .

I even try with single parameter in .json like