-
Notifications
You must be signed in to change notification settings - Fork 24.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move MinIO fixture in its own fixture project #48921
Conversation
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs an @atorok review :) All I can point out is that there's some merge conflict in the build file.
Probably from changing the default parameters for the S3 endpoint (I think you did that in some other PR as well a few days back)
@original-brownbear Just wanted you to be OK with moving this to a fixture :) And sorry for the conflicts, #48849 was merged 2 hours and I did not notice. |
@tlrx ah ok, thanks for checking -> I'm good with this if Alpar is :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@elasticmachine update branch |
This commit moves the MinIO docker-compose fixture from the :plugins:repository-s3 to its own :test:minio-fixture Gradle project.
This pull request moves the MinIO docker-compose fixture from the
:plugins:repository-s3
to its own:test:minio-fixture
Gradle project.The goal here is to make the fixture more easily reusable and also makes the
repository-s3
build Gradle file a bit more comprehensive.