Skip to content

Images: Changed how new image permissions are set #5601

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

Merged
merged 1 commit into from
May 5, 2025

Conversation

ssddanbrown
Copy link
Member

Removed default public visibility for images at the driver level, leaving only doing this as a specific action in the logic. Added try/catch around permission setting so that
permission-incompatible environments won't fatally fail, but instead log a warning.

Tested via a google cloud storage bucket FUSE mount, mounted under another user but with open 777 permissions.

Related to #5269

Removed default public visibility for images at the driver level,
leaving only doing this as a specific action in the logic.
Added try/catch around permission setting so that
permission-incompatible environments won't fatally fail, but instead
log a warning.

Tested via a google cloud storage bucket FUSE mount, mounted under another
user but with open 777 permissions.

Related to #5269
@ssddanbrown ssddanbrown added this to the v25.02.3 milestone May 3, 2025
@ssddanbrown ssddanbrown merged commit 642ba66 into development May 5, 2025
17 checks passed
@ssddanbrown ssddanbrown deleted the file_permissions branch May 5, 2025 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant