Mise is aware of, but doesn't apply env variable expansions from multiple files

[jmoppel]

I have an issue with variable expansion in .env files. I don't think it is a dotenvy problem. Essentially, two of of my environment variables are blank that use env variable expansion. However, when I issue mise envs, it shows the correctly expanded values.

I have two env files .postgres and .local.

[env]
_.file = [
    ".envs/.dev/.postgres",
    ".envs/.dev/.local",
]

# .postgres
PGHOST=postgres

# .local
PGTEST="${PGHOST}"
PGTESTING=$PGHOST

The PGTEST and PGTESTING env variable values are returning blank.

$ printenv |grep PG
PGTESTING=
PGTEST=
PGHOST=postgres

However, when I run mise envs, it shows the proper exports.

...
export PGHOST=postgres
export PGTEST=postgres
export PGTESTING=postgres
...

I realize this usage isn't covered in the docs, but thought I'd check and see if I need to configure things differently. For now, I'm just loading the env files with hooks, so I have a workaround.

Mise doctor output

mise doctor
version: 2024.12.10 linux-x64 (d52ec61 2024-12-14)
activated: yes
shims_on_path: no

build_info:
  Target: x86_64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS, OPENSSL
  Built: Sat, 14 Dec 2024 18:47:35 +0000
  Rust Version: rustc 1.83.0 (90b35a623 2024-11-26)
  Profile: release

shell:
  /bin/bash
  GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2020 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

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

config_files:
  ~/.config/mise/config.toml
  ~/src/example/.python-version
  ~/src/example/mise.toml

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

plugins:

toolset:
  aqua:BurntSushi/[email protected]
  aqua:astral-sh/[email protected]
  aqua:caddyserver/[email protected]
  aqua:docker/[email protected]
  core:[email protected]
  core:[email protected]

path:
  ~/.local/share/mise/installs/caddy/2.8.4
  ~/.local/share/mise/installs/docker-compose/1.29.2
  ~/.local/share/mise/installs/node/22.12.0/bin
  ~/.local/share/mise/installs/ripgrep/14.1.1/ripgrep-14.1.1-x86_64-unknown-linux-musl
  ~/.local/share/mise/installs/uv/0.5.6/uv-x86_64-unknown-linux-musl
  ~/.local/share/mise/installs/python/3.12.7/bin
  ~/.local/bin
  ~/bin
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  /snap/bin

env_vars:
  MISE_SHELL=bash

settings:
  experimental                          true                ~/src/example/mise.toml
  idiomatic_version_file_disable_tools  [".python_version"] ~/src/example/mise.toml

1 problem found:

1. new mise version 2024.12.24 available, currently on 2024.12.10

[jmoppel]

Update: I reread the docs again the Multiple env._ Directives section, and tried using multiple [[env]] sections as shown below.

[[env]]
_.file = ".envs/.dev/.postgres"

[[env]]
_.file = ".envs/.dev/.local"

That still didn't seem to work either.

[syhol]

Something weird going on here. Sometimes I can recreate your problem and sometimes it works as you want.

I thought it might have something to do with the order the files are imported, either based on the updated/created timestamps or alphabetical, but I can't reliably reproduce anything.