Use environment variable with --config environment #59
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is a fix for #57.
It is now possible to use environment variables instead of a configuration file.
Motivation and Context
This is helpful if you want to run pc within a CI/CD pipeline.
How Has This Been Tested?
By setting the environment variables:
PC_SAAS_API_ENDPOINT
PC_COMPUTE_API_ENDPOINT
PC_ACCESS_KEY
PC_SECRET_KEY
And then run pc referring to a configuration called environment:
pc --config environment ...Types of changes
Checklist