Support custom s3 endpoint for Match storage #19929
Closed
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.
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validMotivation and Context
Our company no longer exposes git repos (where we were storing mobile certs) to BitRise (where we are running
match
from). We can, however, store certs on our own instance of Minio, an open source S3, and expose it to BitRise.Description
This PR adds
fastlane match
options to support custom S3 endpoints.Testing Steps
Setup a local Minio server
Create Minio bucket
Configure a
Matchfile
like this:Run match
Check for files with
mc ls
: