Is your feature request related to a problem? Please describe.
tenv already supports custom remotes and advanced remote configuration, which is very useful for companies that use artifact mirrors, private registries, or internal proxies.
However, some environments do not have reliable access to public APIs, GitHub release pages, HashiCorp release endpoints, or even internal HTTP mirrors. This is common for air-gapped installations, restricted CI runners, secure enterprise networks, and prebuilt container images.
In these cases, the required tool binary may already be available locally or through a controlled internal process, but tenv still needs to resolve a version constraint against the list of available versions. Today this flow generally assumes that the release list can be fetched from an HTTP/API source.
It would be useful if tenv could read the release/version list from a local file as well.
Describe the solution you'd like
Allow release list URLs to use the file:// scheme, so tenv can resolve versions from a local file without making a network request.
Example:
TFENV_LIST_URL=file:///opt/tenv/releases/terraform/index.json tenv tf install
Is your feature request related to a problem? Please describe.
tenvalready supports custom remotes and advanced remote configuration, which is very useful for companies that use artifact mirrors, private registries, or internal proxies.However, some environments do not have reliable access to public APIs, GitHub release pages, HashiCorp release endpoints, or even internal HTTP mirrors. This is common for air-gapped installations, restricted CI runners, secure enterprise networks, and prebuilt container images.
In these cases, the required tool binary may already be available locally or through a controlled internal process, but
tenvstill needs to resolve a version constraint against the list of available versions. Today this flow generally assumes that the release list can be fetched from an HTTP/API source.It would be useful if
tenvcould read the release/version list from a local file as well.Describe the solution you'd like
Allow release list URLs to use the
file://scheme, sotenvcan resolve versions from a local file without making a network request.Example: