fix(cache-cli): allow custom S3 endpoint to be used #467
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.
https://github.com/renderedtext/tasks/issues/6905
Issue
Currently, we only use a custom S3 (minio) during our tests, so we are hardcoding the minio credentials. That blocks from using a custom S3 server.
Solution
We make the custom S3 path configurable as well, and allow the key/secret pair to be configured through environment variables. One can either:
AWS_*ones)SEMAPHORE_CACHE_*ones are not set, we default to using the default AWS ones.Other changes