-
Notifications
You must be signed in to change notification settings - Fork 430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Environment variables in az.conf causing error #2185
Comments
The environment variable exists and is correctly set. To view spots where the error occurs, run |
az worker is community based, so you need to wait till community who has AZ fixes it or you can check how to fix it |
@doomedraven Thank you for the reply. I will be looking into potential fixes until someone with more knowledge comes along. |
I have entered a python shell in Found a work-around until a fix is in place. I used |
Hi @ChrisThibodeaux, can you confirm if this is something only happening for this environment variable (namely subscription_id) you did face this for others as well ? Also could you give the full trace for the error in question ? |
@cccs-mog I will try that for each env var In |
About accounts on capesandbox.com
This is open source and you are getting free support so be friendly!
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
Placing an env variable as such to work:
subscription_id = %(ENV:SUBSCRIPTION_ID)s
Current Behavior
Errors out with a
configparser.InterpolationMissingOptionError
Failure Information (for bugs)
configparser.InterpolationMissingOptionError: Bad value substitution: option 'subscription_id' in section 'az' contains an interpolation key 'env:subscription_id' which is not a valid option name. Raw value: '%(ENV:SUBSCRIPTION_ID)s'
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
Context
Deploying in Azure while following the docs.
$ git log | head -n1
to find outFailure Logs
Please include any relevant log snippets or files here.
The text was updated successfully, but these errors were encountered: