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

未关闭
#2,824 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
go, python
领域
cli, devtools

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
Go
星标
12.4k
派生
358
平均合并
17 小时 12 分钟
30 天内合并 PR
31

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

jetify-com/devbox 的其他 Issue

查看 jetify-com/devbox 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。