azure-gate: NixOS-safe bicep — nixpkgs#bicep on PATH + use_binary_from_path #153
No reviewers
Labels
No labels
bug
discussion
duplicate
enhancement
goal
help wanted
horizon:backlog
horizon:governance
horizon:mvp
invalid
operator-decision
question
roadmap
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-platform/mitosis!153
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/azure-gate-nixos-bicep"
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?
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
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.