Issue #1356: It should be possible not to use the visibility handler/visibility settings. #1357
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jkuma
changed the title
…ity handler/visibility settings.
|
@jkuma thank you for your contribution, it's released as 2.3.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
See related issue #1356
The Uniform bucket-level access doesn't accept the predefinedAcl option to be set when performing actions on objects. I tried all default acl options, even null, and it ends up with following error: Cannot insert legacy ACL for an object when uniform bucket-level access is enabled
Proposed solution
In order to ensure backward compatibility, it should be nice to have a new constant to bypass this settings.