feat: add a field to disable the auto mutation of endpoints to S3 com… #733
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.
…patible services
What's changed and what's your intention?
PLEASE DO NOT LEAVE THIS EMPTY !!!
Please explain IN DETAIL what the changes are in this PR and why they are needed:
At the time of writing, RisingWave will automatically mutate the endpoint to a virtual hosted style. It's a bit confusing and will cause problems when a user is using a S3 compatible service that doesn't support accessing with virtual hosted style endpoints.
The PR adds a field
disableAutomaticVirtualHostStyle
under thespec.stateStore.s3
to let the user decide when to disable the automatic change of style. Recommended ways to explicitly set the styles are as follows.The field takes effect by setting environment variable
RW_IS_FORCE_PATH_STYLE=true
in containers.Checklist
Refer to a related PR or issue link (optional)