Fragmented config does not respect MISE_CONFIG_DIR

[tmeijn]

Describe the bug
Fragmented configs, introduced in #3273, does not seem to respect MISE_CONFIG_DIR when set to a different path.

To Reproduce

❯ docker run -it --rm --entrypoint bash jdxcode/mise:v2024.12.3
root@8b111b333193:/mise# mkdir -p conf.d      
root@8b111b333193:/mise# echo "[tools]" >> conf.d/test.toml
root@8b111b333193:/mise# echo '"ubi:dummy/package" = "latest"' >> conf.d/test.toml 
root@8b111b333193:/mise# cat conf.d/test.toml 
[tools]
"ubi:dummy/package" = "latest"

root@8b111b333193:/mise# mise doctor
version: 2024.12.3 linux-arm64 (0e849fc 2024-12-08)
activated: no
shims_on_path: yes

build_info:
  Target: aarch64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS
  Built: Sun, 8 Dec 2024 17:17:14 +0000
  Rust Version: rustc 1.83.0 (90b35a623 2024-11-26)
  Profile: release

shell:
  (unknown)

dirs:
  cache: /mise/cache
  config: /mise
  data: /mise
  shims: /mise/shims
  state: ~/.local/state/mise

config_files:
  /mise/config.toml

backends:
  aqua
  asdf
  cargo
  core
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:

toolset:
  core:python@3.13.1

env_vars:
  MISE_DATA_DIR=/mise
  MISE_CACHE_DIR=/mise/cache
  MISE_CONFIG_DIR=/mise

settings:

No problems found

Note that the the config file is not on path.

Expected behavior
I would expect mise to pick up the created configuration file.

mise doctor output

root@8b111b333193:/mise# mise doctor
version: 2024.12.3 linux-arm64 (0e849fc 2024-12-08)
activated: no
shims_on_path: yes

build_info:
  Target: aarch64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS
  Built: Sun, 8 Dec 2024 17:17:14 +0000
  Rust Version: rustc 1.83.0 (90b35a623 2024-11-26)
  Profile: release

shell:
  (unknown)

dirs:
  cache: /mise/cache
  config: /mise
  data: /mise
  shims: /mise/shims
  state: ~/.local/state/mise

config_files:
  /mise/config.toml

backends:
  aqua
  asdf
  cargo
  core
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:

toolset:
  core:python@3.13.1

env_vars:
  MISE_DATA_DIR=/mise
  MISE_CACHE_DIR=/mise/cache
  MISE_CONFIG_DIR=/mise

settings:

No problems found

Additional context
Add any other context about the problem here. Consider running mise with --debug or --trace for extra debug info.

[syhol]

If MISE_DATA_DIR=/mise then .config/mise/conf.d/*.toml would resolve to /mise/.config/mise/conf.d/*.toml.

If I do this it works

❯ docker run -it --rm --entrypoint bash jdxcode/mise:v2024.12.3
root@01cec1b8c428:/mise# mkdir -p .config/mise/conf.d     
root@01cec1b8c428:/mise# echo "[tools]" >> .config/mise/conf.d/test.toml
root@01cec1b8c428:/mise# echo '"ubi:dummy/package" = "latest"' >> .config/mise/conf.d/test.toml 
root@01cec1b8c428:/mise# cat .config/mise/conf.d/test.toml 
[tools]
"ubi:dummy/package" = "latest"
root@8b111b333193:/mise# mise doctor
version: 2024.12.3 linux-arm64 (0e849fc 2024-12-08)
activated: no
shims_on_path: yes

build_info:
  Target: aarch64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS
  Built: Sun, 8 Dec 2024 17:17:14 +0000
  Rust Version: rustc 1.83.0 (90b35a623 2024-11-26)
  Profile: release

shell:
  (unknown)

dirs:
  cache: /mise/cache
  config: /mise
  data: /mise
  shims: /mise/shims
  state: ~/.local/state/mise
mise /mise/.config/mise/conf.d/test.toml is not trusted. Trust it? Yes

config_files:
  /mise/config.toml
  /mise/.config/mise/conf.d/test.toml

backends:
  aqua
  asdf
  cargo
  core
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:
mise WARN  failed to resolve toolset: [/mise/.config/mise/conf.d/test.toml] ubi:dummy/package@latest: HTTP status client error (404 Not Found) for url (https://api.github.com/repos/dummy/package/releases)

toolset:
  core:python@3.13.1

env_vars:
  MISE_DATA_DIR=/mise
  MISE_CACHE_DIR=/mise/cache
  MISE_CONFIG_DIR=/mise

settings:

No problems found

It looks like the .config/mise/ bit is not optional and must come after MISE_CONFIG_DIR, which makes sense to me.

[jdx]

It looks like the .config/mise/ bit is not optional and must come after MISE_CONFIG_DIR, which makes sense to me.

hmm no I think OP is right here. I would expect MISE_CONFIG_DIR=/foo to use /foo/conf.d/*.toml