🤖 AI-Generated Summary of Archived Issue

This discussion summarizes the archived GitHub issue #1448 about executing arbitrary scripts to export environment variables.

Original Issue

Title: env._.run

Description:
Similar to issue #1447, the request was to make it possible to execute arbitrary scripts which "export" environment variables using a syntax like:

[env]
_.run = "./myscript"

Unlike #1447, this would run like any other binary and somehow pull env vars out of it. The issue mentioned that direnv has a trick where they launch direnv inside of the script to pull the env vars out.

Key Discussion Points

1. Use Cases:

   • Loading env vars from 1Password
   • Running docker compose up automatically when entering project directories
   • Executing scripts on directory change
   • Single atomic commands for environment setup

2. Implementation: The feature was implemented through the hooks system in mise, which allows running scripts and sourcing their output to modify the environment.

3. Alternative Solution - Templating: One user noted that mise's templating system can achieve similar results:

   [env]
   TF_VAR_github_token = "{{ exec(command='gh auth token') }}"

   This works with password managers like Bitwarden CLI as well.

4. PATH Modification Issue: Some users reported difficulty adding to PATH using hooks, with MISE_ADD_PATH not working as expected in hook scripts.

Resolution

The feature was implemented through mise's hooks system. Users can now:

• Use shell hooks to execute scripts on directory changes
• Source hook output to modify environment variables
• Use templating with exec() for inline command execution

See: https://mise.jdx.dev/hooks.html

Related Documentation

• Original issue: https://github.com/jdx/mise/issues/1448
• Hooks documentation: https://mise.jdx.dev/hooks.html
• Environment templating: https://mise.jdx.dev/environments/#templates

This is an archived issue summary. Issues have been disabled in favor of GitHub Discussions for better community engagement.