Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add plugin specific ENV? #1798

Closed
h3adache opened this issue Mar 18, 2024 · 2 comments · Fixed by #3622
Closed

Add plugin specific ENV? #1798

h3adache opened this issue Mar 18, 2024 · 2 comments · Fixed by #3622

Comments

@h3adache
Copy link

Is it possible to override ENV for just one specific plugin?
I am facing an issue where an older version of teleport-ent was not built for darwin-amd64.

This results in an error when we try to just run mise install

mise install
curl: (22) The requested URL returned error: 404
mise ~/.local/share/mise/plugins/teleport-ent/bin/download failed
* Downloading teleport-ent release 11.3.11...
curl: (22) The requested URL returned error: 404
asdf-teleport-ent: Could not download https://cdn.teleport.dev/teleport-ent-v11.3.11-darwin-arm64-bin.tar.gz
mise ~/.local/share/mise/plugins/teleport-ent/bin/download exited with non-zero status: exit code 1
mise Run with --verbose or MISE_VERBOSE=1 for more information

The workaround is to run with ARCH

ARCH=amd64 mise install teleport-ent 11.3.11

But it could be nice for this and future scenarios if env could be targeted to plugins. e.g.

[env]
TELEPORT_ENT_ARCH=amd64
@jdx
Copy link
Owner

jdx commented Mar 18, 2024

this is impossible. mise would need to wrap every command but that simply is not how it works

edit: sorry I misunderstood, I thought you were asking when something is executed. It would be possible to have something run only during plugin installation

@jdx
Copy link
Owner

jdx commented Nov 30, 2024

I think we should have a tool option for env:

[tools]
teleport-ent = { version = "11.3.11", install_env = { TELEPORT_ENT_ARCH = "amd64" } }

jdx added a commit that referenced this issue Dec 16, 2024
jdx added a commit that referenced this issue Dec 16, 2024
@jdx jdx closed this as completed in #3622 Dec 16, 2024
@jdx jdx closed this as completed in 9e4fd90 Dec 16, 2024
miguelmig pushed a commit to miguelmig/mise that referenced this issue Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants