Skip to content

4.1.0

Choose a tag to compare

View all tags
@JoshuaHarris391 JoshuaHarris391 released this 26 Aug 03:03
4.1.0
2921fa3

Breaking Changes

  • The marker studies: block is no longer read. The study registry now lives in the env's SSM tree; a one-time notice points at g3dt study migrate (2921fa3)

Features

  • Add the g3dt study command group — the registry that decides what metadata upload sends to a commons moves from s3://<metadata-bucket>/config/studies.yaml into per-study SSM parameters (/{project}/{env}/studies/<name>, one atomic JSON parameter each):
    • study list / study show — script-friendly listing and a per-study liveness check (DataImportOrder.txt + node-JSON count, the exact upload preflight)
    • study add / study set / study remove — validated, atomic per-study writes with typed production gates
    • study repoint --release <tag>|--latest — the release-cutover verb: swaps each path's vX.Y.Z segment, validates every target before writing anything (one bad target writes nothing), reads --latest from the releases ledger, supports --dry-run
    • study migrate — all-or-nothing import of the legacy studies.yaml, verified by re-reading SSM before the file is renamed to .migrated; idempotent
  • Guided errors throughout: misses list the actually-registered studies with a did-you-mean; an empty registry prints copy-pasteable study add/study migrate commands; auth failures propagate with an aws sso login hint instead of masquerading as "no studies configured"
  • Environment separation is structural: the SSM path is the env, retiring the {study}_{env} key-suffix convention and its bare-key fallback trap; lookups stay case-forgiving and accept the legacy suffixed wire form, so dispatched service scripts need no changes
  • Mutating commands refuse to run while the legacy S3 registry still serves (writing to SSM would silently shadow the whole file) — study migrate is the only bridge
  • config studies becomes an alias of study list; config show --study unchanged on the surface, new resolver underneath
  • New normative design doc: docs/design/studies.md

Deprecations

  • The S3 config/studies.yaml fallback remains readable with a once-per-process warning and is removed in 5.0, keeping EC2 job boxes on older pinned toolkits working until each env migrates

Full Changelog: 4.0.1...4.1.0

Assets 2
Loading