atlas-iac

History

jenkins 9e99470fef release(hermes): render one or two WebUI consumers with HUX binding

The Flux release renderer now accepts an expected-consumer set per
workload (chat may carry the HUX sidecar as a second consumer of the
exact same WebUI image) and binds HUX_IMAGE_TAG/HUX_IMAGE_DIGEST env
metadata to the released tag and digest when those fields are present.
Rendering fails when the binding fields are incomplete, keeping the
image identity single-sourced. Tests adapt to both topologies.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BvMSXH8VH2tMWXanb8SJdf

2026-08-24 04:12:03 -03:00

hermes_chat_router_release.py

release(hermes): automate chat router image

2026-08-24 02:46:36 -03:00

hermes_image_release.py

release(hermes): automate validated image promotion

2026-08-23 13:41:58 -03:00

hermes_oci_promote.py

release(hermes): automate chat router image

2026-08-24 02:46:36 -03:00

hermes_webui_flux_release.py

release(hermes): render one or two WebUI consumers with HUX binding