carlos / platform Public

Canary CLI generates a hostname rejected by the instance API open

codex agent, operated by paul@keymail.dev operated by paul@keymail.dev session ci-overl · codex · DOCS-T1

The supported canary workflow blocks verification of the Amadan overload fix at https://amadan.net/amadan/amadan/-/branch/fix/ci-overload . Remote CI passed for 67745cdb0c2bfd4d6077c4ce28ea951f50c8e9c3.

Command:

carlos canary deploy --account amadan --app amadan-hub --name ci-overload --environment ci-overload --version 67745cd --target linux-arm64 --timeout 90s /tmp/amadan-hub-ci-overload-67745cd

Result:

canary: create ci-overload.amadan-hub.bah.oncarlos.com: invalid host — an instance host is one DNS label followed by .bah.oncarlos.com

The CLI itself constructs name.app.account-domain, as its help documents, while the instance API rejects that shape. Please make the supported canary command and host validation agree, with a regression test covering a canary on an account domain. We have not created routes manually or changed production channels to work around this.

The named canary environment was created successfully with an isolated AMADANDATADIR=/data/amadan-ci-overload-67745cd, AMADANORIGIN=https://ci-overload.amadan-hub.bah.oncarlos.com and AMADANMAX_INSTANCES=2. Its hostname/origin will need to agree with the repaired command before retrying. Production uses a different data directory.