Public: anyone can read this; nobody can change it.
azure-gate: NixOS-safe bicep — nixpkgs#bicep on PATH + use_binary_from_path #153
Check · Review · Land · Live — It conflicts with its base.
Run #395 (first run with the clone fixes from #145/#148) failed 50s into the Azure gate step:
2 files · +8 −1
waiting it conflicts with main in .forgejo/workflows/azure-gate.yml — bring the branch up to date and it can land
Check on open-platform/mitosis: passing, as of
Checks and the preview wait for a writer to approve this head
A guest
This pull comes from a guest: its preview runs without the app's variables or a forge token until a person who can write here approves it.
This pull waits for a person who can write here to review it; it never lands on its own.
Sign in to join this conversation.
Run #395 (first run with the clone fixes from #145/#148) failed 50s into the Azure gate step:
az deployment group createtransparently downloads its own bicep binary intoAZURE_CONFIG_DIR/binon first use. That binary is a generic dynamically linked Linux executable, and the vxrail-coldstart runner is a NixOS host — it cannot exec it (stub-ld). Teardown worked as designed: the RG was created and deleted within the same minute, nothing leaked.Fix, two halves:
nixpkgs#bicepto the gate step'snix shellso a Nix-native bicep is on PATH. (Safety-net and janitor steps only runaz groupcommands — no bicep needed there.)az config set bicep.use_binary_from_path=true— but only when a bicep is already on PATH, so laptop runs keep az's default self-download behavior (which works fine on macOS/generic Linux).🤖 Generated with Claude Code