Rewrite changelog registry docs for scrubber Lambda ownership - #3761
Open
cotti wants to merge 1 commit into
Open
Rewrite changelog registry docs for scrubber Lambda ownership#3761cotti wants to merge 1 commit into
cotti wants to merge 1 commit into
Conversation
The registry docs still described the retired model: client-side refresh, registry pass-through, pre-scrub ETags, a 1 h CloudFront TTL (caching is disabled), and a refresh "skipped for --artifact-type changelog". Documents the reconciler as sole producer, the public-object ETag, convergence semantics, absent-vs-empty manifests, the reconcile message contract, and the registry reconcile/verify operator commands (docs-eng-team#688 Phase 4).
cotti
force-pushed
the
changelog-registry-docs
branch
from
August 4, 2026 01:50
7af75b0 to
9bebf38
Compare
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
1 participant
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.
Why
Phase 4 of elastic/docs-eng-team#688, stacked on #3760. After Phases 1–3 the registry docs described a retired system: client-side refresh, registry pass-through, an ETag "documented as useless", a CloudFront "1 h TTL" that hasn't existed since caching was disabled, and a claim that the refresh was "skipped for
--artifact-type changelog".What
docs/development/changelog-bundle-registry.mdnow documents the end state: the scrubber Lambda'sRegistryReconcileras the manifest's sole producer (registry = f(state)), theproducerfield,bundles[].etagas the public object's ETag (finally usable for CDN cache revalidation), consistency stated as convergence with the consumer's listed-but-missing tolerance kept, the deliberate absent ≠ empty manifest semantics, and theregistry reconcile/registry verifyoperator tooling with the reconcile message contract. The scrubber README's event-handling section andcmd-upload.md's registry paragraph are aligned with the same model.Part of elastic/docs-eng-team#688 (Phase 4).