Issue with hardcoded airbyte minio image in minio.yaml file

Summary

The user is facing an issue with the airbyte minio image being hardcoded into the minio.yaml file. They found a related GitHub issue and a proposed solution, but the merge did not happen and the issue persists after half a year.


Question

Hey all! We are facing an issue with the airbyte minio image being hardcoded into the minio.yaml file. I found this (https://github.com/airbytehq/airbyte/issues/34825) and this solution (https://github.com/airbytehq/airbyte-platform/pull/303) but for some reason the merge did not happen and after a half year the issue still exists.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["issue", "hardcoded", "airbyte-minio-image", "minio.yaml", "github-issue", "merge", "airbyte-platform"]