Skip to content

Preserve Scaleway object ACLs during bucket synchronization - #44

Merged
davidvanleeuwen merged 4 commits into
mainfrom
fix/bucket-policy-sync
Nov 9, 2026
Merged

davidvanleeuwen merged 4 commits into
mainfrom
fix/bucket-policy-sync

Conversation

@davidvanleeuwen

@davidvanleeuwen davidvanleeuwen commented Nov 9, 2026 •

Copy link
Copy Markdown
Member

✨ What changes

Ordinary Scaleway bucket synchronization no longer installs a bucket-wide public-read policy, which could override private object ACLs. Storage sync failures also no longer abort an enclosing database transaction when the caller handles the error and continues.

  • Update CORS without reading, replacing or deleting policies on Scaleway when hotlink protection is disabled.
  • Preserve explicit policies for protected media and existing behavior for other storage providers.
  • Keep the row lock and returned storage errors; add regressions for policy-free synchronization and usable outer transactions.
  • Update locked Ecto to 3.14.3 to resolve CVE-2026-118391, which blocked the dependency audit.

🔎 Additional checks

An isolated API creation scenario completed with an API key using only bucket HEAD and CORS requests, with no policy request. The earlier simulated HTTP 400 scenario also succeeds after the transaction fix. No live storage settings were changed.

@davidvanleeuwen davidvanleeuwen changed the title Keep bucket sync failures from aborting caller transactions Preserve Scaleway object ACLs during bucket synchronization Nov 9, 2026
@davidvanleeuwen
davidvanleeuwen merged commit b16df99 into main Nov 9, 2026
6 checks passed
@davidvanleeuwen
davidvanleeuwen deleted the fix/bucket-policy-sync branch November 9, 2026 09:45
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.

1 participant