Closed jamesharling closed 5 months ago
When supplying environment variables to the action, it asks for them. in the format
environmentVariables: ENV1=value1 ENV2=value2
however this is cumbersome to manage in a workflow. YAML supports multi-line strings such as:
environmentVariables: | ENV1=value1 \ ENV2=value2
However this appears to be passed literally to the action, which then fails at deployment time:
/usr/bin/az containerapp update -n containerApp -g rg-containerApp --output none --replace-env-vars ENV1=value1 \ ENV2=value2
ERROR: (ContainerAppInvalidEnvVarName) Env variable name '\
Am I doing something wrong here, or is this not supported?
Now solved, this needed to be done using the folding syntax:
environmentVariables: > ENV1=value1 ENV2=value2
When supplying environment variables to the action, it asks for them. in the format
however this is cumbersome to manage in a workflow. YAML supports multi-line strings such as:
However this appears to be passed literally to the action, which then fails at deployment time:
Am I doing something wrong here, or is this not supported?