DIG-1835: make a self-contained init-minio make target #877
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.
I thought that the best way to achieve the goal of having an optional minio server would be to pull all of those bits out of the main make compose targets and consolidate them into one
init-minio
target. This way, if a user wants to set up a MinIO S3 store for testing or dev, they can easily do so. The access key and secret key are in tmp/secrets.I removed the candigv2 label from the minio container/image/volumes because otherwise clean-all will grab these too. If you want to get rid of the minio container completely,
make clean-minio
works.To test: run
make init-minio
. You should then have a minio container with its api visible at port 9000. If you runmake clean-all
, the minio container should remain and still be accessible. Runningmake clean-minio
should get rid of it.