Admin Provision form: default Node SID should fall back to core/TFGRID_NODE_IDS #15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
crates/hero_tfgrid_deployer_admin/src/routes.rs:60-62:The help text under the Node SID input on the Provision form reads "Defaults from
core/TFGRID_NODE_IDSif set." but the helper only checksDEPLOYER_DEFAULT_NODE_SID. On VM 0069 onlycore/TFGRID_NODE_IDS=5is set (in the hero_proc secret store), so the field is empty and the admin has to type the node sid manually.Two fix shapes, either works:
DEPLOYER_DEFAULT_NODE_SID=005din the hero_proc secret store on every admin VM. Document in admin-vm-deployment-runbook.md. No code change. Mismatched help text needs updating either way.core/TFGRID_NODE_IDSfrom hero_proc secrets and translates the numeric grid node id to the local 4-char sid by asking the colocated compute daemon. Closer to what the help text claims and what an operator would expect, but requires the compute daemon to be reachable (blocked today by hero_os_tfgrid_deployer#13).Either way, the help text and the helper should agree.
Fixed by squash-merge
c649d76ondevelopment— help text under the Node SID input now matches reality (readsDEPLOYER_DEFAULT_NODE_SIDenv). Operationally also setDEPLOYER_DEFAULT_NODE_SID=005don VM0069via hero_proc secret. The canonical hero_proc-secret-driven helper refactor (so other admins do not need to hand-edit env) is left as a follow-up.