docs: record CORS trust and explicit version delete authorization - #11
Merged
Conversation
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>
Deploying silo-pgsty-com with
|
| 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 |
This was referenced Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Publish the operator-facing documentation for the server candidates in:
s3:DeleteObjectVersionwhile trusted replication retains the documented target policy.Changes include:
versionId=null;DeleteObjectsper-entrys3:versionidcondition behavior;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 verifyPASS;--panicOnWarningPASS;The original site worktree's manual
data/home/metrics.yamlchange and untracked Console 2.3.0 drafts were isolated in another worktree and are not part of this PR.