The Infisical CLI should respect the --domain flag/INFISICAL_API_URL environment variable, bypassing the manual domain entry for self-hosted instances during login. Currently, even when specifying these parameters, users are prompted to input the domain manually.
This would make the CLI more user & script-friendly, particularly in scenarios where shell scripts use the CLI, and the user's session expires.
I currently use this expect script in my shell scripts to automate the domain input.
A way to bypass the prompt (or a flag like --self-hosted) would eliminate the need for these workarounds.
To Reproduce
Steps to reproduce the behavior:
Set INFISICAL_API_URL or --domain to a self-hosted instance
run infisical login
Expected behavior
When using the CLI for a self-hosted instance, the flow should be entirely non-interactive after providing the necessary environment variables or flags (other than the user passing in the token).
For example:
$ export INFISICAL_API_URL="https://infisical.example.com/"
$ infisical login
✔ Self Hosting
Domain: https://infisical.example.com
To complete your login, open this address in your browser: https://infisical.example.com/login?callback_port=1234
...
Token:
Describe the bug
The Infisical CLI should respect the
--domain
flag/INFISICAL_API_URL
environment variable, bypassing the manual domain entry for self-hosted instances during login. Currently, even when specifying these parameters, users are prompted to input the domain manually.This would make the CLI more user & script-friendly, particularly in scenarios where shell scripts use the CLI, and the user's session expires. I currently use this expect script in my shell scripts to automate the domain input. A way to bypass the prompt (or a flag like
--self-hosted
) would eliminate the need for these workarounds.To Reproduce
Steps to reproduce the behavior:
INFISICAL_API_URL
or--domain
to a self-hosted instanceinfisical login
Expected behavior
When using the CLI for a self-hosted instance, the flow should be entirely non-interactive after providing the necessary environment variables or flags (other than the user passing in the token).
For example:
Screenshots
Platform you are having the issue on:
Linux