Skip to content

docs: record CORS trust and explicit version delete authorization - #11

Merged
Vonng merged 3 commits into
mainfrom
codex/delete-version-authz-docs
Sep 1, 2026
Merged

docs: record CORS trust and explicit version delete authorization#11
Vonng merged 3 commits into
mainfrom
codex/delete-version-authz-docs

Conversation

@Vonng

@Vonng Vonng commented Sep 1, 2026

Copy link
Copy Markdown
Member

Summary

Publish the operator-facing documentation for the server candidates in:

  • pgsty/silo#101: resident-only pre-auth CORS and unified replication request trust;
  • pgsty/silo#104: explicit-version deletes use s3:DeleteObjectVersion while trusted replication retains the documented target policy.

Changes include:

  • a bilingual design record for CORS and replication trust, including evidence and unreleased status boundaries;
  • an EN/ZH release note for issue #58 and PR #104;
  • corrected Object Deletion permission matrices for no version ID, UUID, and versionId=null;
  • DeleteObjects per-entry s3:versionid condition behavior;
  • IAM policy-action clarifications;
  • bucket-replication target policy compatibility notes;
  • trust-design clarification that ReplicateDelete is the trust gate while the receiver also preserves DeleteObject and explicit version-deny checks.

Compatibility and release boundary

The release note explicitly states that publication does not imply a merged server change, release artifact, image, package, deployment, or production verification. Ordinary DeleteObject-only principals lose named-version deletion only when a release containing #104 is deployed. Replication target policies do not add DeleteObjectVersion.

Verification

  • go mod verify PASS;
  • strict Hugo build with --panicOnWarning PASS;
  • EN/ZH each render 1,185 pages;
  • 476,433 internal references across 1,381 HTML files PASS;
  • new EN/ZH release routes exist with reciprocal canonical/hreflang links;
  • no trailing whitespace or diff-check errors.

The original site worktree's manual data/home/metrics.yaml change and untracked Console 2.3.0 drafts were isolated in another worktree and are not part of this PR.

Record the resident-only CORS hot path, unified replication trust decisions, compatibility evidence, and residual risks in English and Chinese. Link the earlier replication-header advisory to the broader design record.

Signed-off-by: Feng Ruohang <rh@vonng.com>
Publish the EN/ZH DeleteObject versus DeleteObjectVersion matrix, replication target compatibility contract, policy-condition behavior, upgrade impact, and pre-release status for issue #58.

Signed-off-by: Feng Ruohang <rh@vonng.com>
Point the trust design record at PR #101 and the explicit-version authorization release note at PR #104 while preserving separate CI, merge, release, and deployment gates.

Signed-off-by: Feng Ruohang <rh@vonng.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying silo-pgsty-com with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0a54b96
Status: ✅  Deploy successful!
Preview URL: https://487efd39.silo-pgsty-com.pages.dev
Branch Preview URL: https://codex-delete-version-authz-d.silo-pgsty-com.pages.dev

View logs

@Vonng
Vonng merged commit 0b8e495 into main Sep 1, 2026
1 check passed
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