-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
revert: "chore(batch-exports): Revert "chore: upgrade minio"" #29189
revert: "chore(batch-exports): Revert "chore: upgrade minio"" #29189
Conversation
This reverts commit 75274e5.
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.
PR Summary
This PR re-upgrades the MinIO object storage service from a 2022 version to a 2025 version, reverting a previous reversion that was made due to failing tests.
- Updated MinIO image in
docker-compose.base.yml
from RELEASE.2022-06-25T15-50-16Z to RELEASE.2025-02-18T16-25-55Z - The upgrade is targeted at self-hosted environments only, as MinIO is not used in production
- The PR aims to fix the test failures that caused the original upgrade to be reverted
- The change is isolated to the
objectstorage
service configuration in the Docker Compose file
1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
posthog/temporal/tests/batch_exports/test_s3_batch_export_workflow.py
Outdated
Show resolved
Hide resolved
@@ -122,7 +122,7 @@ services: | |||
DYNAMIC_CONFIG_ENABLED: 'true' | |||
|
|||
objectstorage: | |||
image: minio/minio:RELEASE.2022-06-25T15-50-16Z | |||
image: minio/minio:RELEASE.2025-02-18T16-25-55Z |
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.
this is the version I've validated works for local dev and for self hosted
@@ -168,7 +168,7 @@ async def minio_client(bucket_name): | |||
|
|||
yield minio_client | |||
|
|||
await delete_all_from_s3(minio_client, bucket_name, key_prefix="/") | |||
await delete_all_from_s3(minio_client, bucket_name, key_prefix="") |
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.
the prefix /
was leaving one file behind that was at the root of the bucket...
so I made it the empty string instead 🤷
i'm guessing we don't care @Gilbert09 @rossgray
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.
if it works 🤷
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.
Not sure why that behaviour has changed then but sounds like it should be fine
Reverts #29188
which was a revert of #29166
We still need to upgrade this for self-hosted but need to get tests running in this PR so we can see if it's only incidental that they're failing
We don't use minio in production, so should be totally safe
you can see the failing tests here https://github.com/PostHog/posthog/actions/runs/13521771267/job/37782507932?pr=29136