Skip to content

ct_worker: publish current log metadata schemas - #295

Open
lukevalenta wants to merge 1 commit into
mainfrom
lvalenta/pvc-2929-log-metadata
Open

lukevalenta wants to merge 1 commit into
mainfrom
lvalenta/pvc-2929-log-metadata

Conversation

@lukevalenta

@lukevalenta lukevalenta commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

Addresses PVC-2929.

Summary

  • replace log.v3.json with schema-compliant per-log metadata.json responses
  • align log configuration with the published metadata fields and use lifecycle status to control submissions
  • enforce Chrome's 3-to-12-month temporal interval for production logs at build time
  • publish a filtered operator-list.json, covered by internal dev-log fixtures
  • remove retired Raio, cftest, and pre-2026h2 dev-log configurations; production log configs will be maintained in the internal deployment repository
  • update integration coverage and metadata consumers

Testing

  • cargo clippy --workspace --all-targets -- -Dwarnings -Dclippy::pedantic
  • cargo test
  • cargo fmt --all --check
  • cargo shear
  • BASE_URL=http://localhost:18790 cargo test -p integration_tests --test static_ct_api

Replace the legacy log metadata response with schema-compliant metadata and operator-list endpoints. Remove obsolete configurations that cannot satisfy the new model, validate production shard intervals, and verify responses against vendored schemas.
@lukevalenta
lukevalenta force-pushed the lvalenta/pvc-2929-log-metadata branch from e2edb93 to 02ba528 Compare September 24, 2026 15:14
@lukevalenta
lukevalenta marked this pull request as ready for review September 24, 2026 15:27
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