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

Fix/s3 pubilshing #1241

Merged
merged 10 commits into from
Feb 6, 2024
Merged

Fix/s3 pubilshing #1241

merged 10 commits into from
Feb 6, 2024

Conversation

neolynx
Copy link
Member

@neolynx neolynx commented Jan 13, 2024

Fixes #1223

Description of the Change

Checklist

  • author name in AUTHORS

sf-nwaller and others added 10 commits February 5, 2024 13:31
as per contributor instructions
instead of caching the whole s3 bucket, cache only the pool path. this
requires an additional parameter, and since this is an interface, all
implementations need to follow. might help in other backends too.

closes #1181
When a publishing uses a publish prefix, instead of listing the contents
of the whole bucket under the storage prefix, only list the contents of
the bucket under the storage prefix and publish prefix, and cache it by
publish prefix.
This speeds up publish operations under a prefix.
@neolynx neolynx changed the title Fix/s3 publshing Fix/s3 pubilshing Feb 5, 2024
@neolynx neolynx merged commit eeb5bd7 into master Feb 6, 2024
2 checks passed
@neolynx neolynx deleted the fix/s3-publshing branch February 6, 2024 20:21
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.

"file already exists and is different" after un-publishing package from S3
5 participants