-
Notifications
You must be signed in to change notification settings - Fork 27
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
Use cloud-dev to run Atlas Planned Maintenance tests #94
Use cloud-dev to run Atlas Planned Maintenance tests #94
Conversation
@@ -78,6 +78,8 @@ functions: | |||
EVERGREEN_BUILD_ID: ${build_id} | |||
ATLAS_API_USERNAME: ${atlas_key} | |||
ATLAS_API_PASSWORD: ${atlas_secret} | |||
ATLAS_API_BASE_URL: ${atlas_url} | |||
ATLAS_ORGANIZATION_NAME: ${atlas_organization} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the org name needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the default value in astrolabe
no longer matches the name of the org to which the cloud-dev API key belongs. Instead of changing the default (set here) I instead started using the envvar to configure this value in case it changes again in the future. The envvar to use can be ascertained/modified using this code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that you can also get this information by running astrolabe info default-values
(displays config opt name and corresponding default value) and astrolabe info environment-variables
(displays envvars that can set to configure various opts).
Closes #93