fix: remove escape from TOWER_ACCESS_TOKEN env var #27
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.
Fixes the following error when running on GCP:
When we escape the
TOWER_ACCESS_TOKEN
variable with\
, Google Batch interprets that as a literal string instead of performing variable substitution and craps out. Removal of this results in a successful run as we are able to authenticate, but Batch performs variable expansion during script execution before logging occurs so the token is shown in the logs.Probably not the best practice but I am not sure of how to workaround this. Any ideas?