Bug: Azure CLI extensions from Nix packages are not discoverable in devbox shell

Aperta
  • Qualcosa non va?
#2,824 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go, python
Ambito
cli, devtools

Direzione di ricerca

Start by tracing how Devbox configures package environments and launches commands in the shell, then inspect the Nix wrapper for az and how it handles PYTHONPATH. Reproduce with the listed azure-cli and extension packages and run az extension list; done means the declaratively installed extension is discovered in the Devbox shell.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug p3 processed triage unrelated
What happened?

When managing azure-cli and its extensions declaratively in devbox.json, the az command is unable to discover the extensions, even though the package files are correctly installed in the Nix profile.

This seems to be caused by the Nix wrapper for the az executable, which appears to create an isolated Python environment, ignoring the PYTHONPATH from the parent devbox shell. This prevents the Azure CLI's standard site-packages auto-discovery from working.

This contrasts with other ecosystems like helm, where setting a HELM_PLUGINS environment variable works as expected. The equivalent AZURE_EXTENSION_DIR does not work here because the Nix package for the extension installs it as a Python module (azext_*) rather than in a separate directory structure.

Steps to reproduce

  1. Create a new directory and run devbox init.

  2. Set the devbox.json to the following content:

    {
  "packages": [
    "[email protected]",
    "[email protected]"
  ]
}

  3. Start the shell with devbox shell.

  4. Run the command to list extensions:

    az extension list

  5. (Optional) Confirm the extension's files are present in the environment's site-packages:

    # Path may vary slightly based on python version
ls .devbox/nix/profile/default/lib/python3.13/site-packages/

This will show azext_log_analytics_solution@ and other related files, proving the package was installed by Devbox.

Expected behavior

The az extension list command should discover and list the log-analytics-solution extension, similar to this output:

Name                      Version     State     Type
-----------------------  ---------  --------  ------
log-analytics-solution   1.0.1        Enabled  whl
Actual behavior

The az extension list command returns an empty list, and commands provided by the extension (e.g., az log-analytics-solution) are not found.

Analysis of the Cause

Debug logs from az extension list --debug show that the CLI never attempts to load extensions from any directory (~/.azure/cliextensions, site-packages, or a path from AZURE_EXTENSION_DIR). It seems the Nix wrapper script for az sanitizes the PYTHONPATH, breaking the auto-discovery mechanism that relies on finding azext_* modules.

Workaround

The current pragmatic workaround is to abandon the declarative management of extensions and use the imperative approach:

  1. Only include the core azure-cli in devbox.json.

    { "packages": ["[email protected]"] }

  2. Inside the devbox shell, manually install the extension.

    az extension add --name log-analytics-solution

This works because it installs the extension into ~/.azure/cliextensions, a path the az wrapper knows how to check.

Command

No response

devbox.json
{
  "$schema": "https://raw.githubusercontent.com/jetify-com/devbox/0.17.1/.schema/devbox.schema.json",
  "packages": [
    "[email protected]",
    "[email protected]",
    "[email protected]",
    "[email protected]",
    "[email protected]",
    "[email protected]"
  ],
  "shell": {
    "init_hook": [
      "export SOPS_AGE_KEY_FILE=$(pwd)/.age.agekey"
    ]
  }
}
Devbox version

0.17.1

Nix version

nix (Determinate Nix 3.17.3) 2.33.3

What system does this bug occur on?

macOS (Apple Silicon)

Debug logs

No response

Lingua principale
Go
Stelle
12.4k
Fork
358
Merge medio
17h 12m
PR unite (30g)
31

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di jetify-com/devbox

Tutte le issue di jetify-com/devbox

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.