Skip to content
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 change to S3 is_object, is_bucket checks #4370

Merged
merged 1 commit into from
Sep 20, 2023

Conversation

davisp
Copy link
Contributor

@davisp davisp commented Sep 19, 2023

The is_bucket and is_object methods are now behaving different in 2.17 and returning errors when they wouldn't previously. For now we're reverting to the previous 2.16 behavior.


TYPE: BUG
DESC: Revert change to S3 is_object, is_bucket checks.

@shortcut-integration
Copy link

This pull request has been linked to Shortcut Story #34450: Revert S3.cc logic change for is_object and is_bucket.

The is_bucket and is_object methods are now behaving different in 2.17
and returning errors when they wouldn't previously. For now we're
reverting to the previous 2.16 behavior.
@davisp davisp force-pushed the pd/sc-34450/revert-bad-s3-change branch from 2f8dfe7 to 7d19ed7 Compare September 19, 2023 17:01
@ihnorton ihnorton merged commit f2ee9fa into dev Sep 20, 2023
53 checks passed
@ihnorton ihnorton deleted the pd/sc-34450/revert-bad-s3-change branch September 20, 2023 00:07
@ihnorton ihnorton changed the title Revert change to S3 existence checks Revert change to S3 is_object, is_bucket checks Sep 20, 2023
ihnorton pushed a commit that referenced this pull request Sep 20, 2023
The is_bucket and is_object methods are now behaving different in 2.17 and returning errors when they wouldn't previously. For now we're reverting to the previous 2.16 behavior.

x-ref #4370

---
TYPE: BUG
DESC: Revert change to S3 is_object, is_bucket checks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants