Public Access
docs: add REQ-ID labels to DEVX-162 spec
This commit is contained in:
@@ -24,13 +24,14 @@ race) is preserved as `DEVX-162-registry-push-race-historical.md`.
|
||||
|
||||
## Approach
|
||||
|
||||
1. `src/devx/api_clients.py` — `get_repo_variable` reads `data` first and falls
|
||||
back to `value` for older server/fixture compatibility. Write path unchanged
|
||||
(PUT/POST `{"value": ...}` verified live: 201/204).
|
||||
2. `src/devx/ci/nightly_gate.py` — unknown non-empty status blocks the deploy
|
||||
(fail closed) instead of allowing it. Unset (bootstrap) still allows.
|
||||
3. Tests cover the `data` field, the `value` fallback, and fail-closed unknown
|
||||
status.
|
||||
1. REQ-1: `src/devx/api_clients.py` — `get_repo_variable` reads `data` first
|
||||
and falls back to `value` for older server/fixture compatibility. Write
|
||||
path unchanged (PUT/POST `{"value": ...}` verified live: 201/204).
|
||||
2. REQ-2: `src/devx/ci/nightly_gate.py` — unknown non-empty status blocks the
|
||||
deploy (fail closed) instead of allowing it. Unset (bootstrap) still
|
||||
allows.
|
||||
3. REQ-3: Tests cover the `data` field, the `value` fallback, and fail-closed
|
||||
unknown status.
|
||||
|
||||
## Test Plan
|
||||
|
||||
|
||||
Reference in New Issue
Block a user