feat(gcp): add env vars for buildkite queues and gcp project id #212
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.
Context
There is no functionality that supports population of
gcpProjectId
andqueues
via environment variables. This limits our ability to run this where config is dynamically populated andgcpProjectId
/queues
attributes are a concern of the execution environment and not coupled to binary invocation.Intent
Use
GCP_PROJECT_ID
andBUILDKITE_QUEUE
environment variables to populate config.Notes
gcpProjectID
is an empty string we fall back to the environment variableGCP_PROJECT_ID
.queues
aren't specified (i.e.len(queues) == 0
) we fall back toBUILDKITE_QUEUE
(same as AWS lambda) environment variables.These changes are backwards compatible to existing usage of this binary. Happy to discuss implementation details if maintainers feel otherwise :)
Reviewers
@triarius @DrJosh9000 PTAL.