-
Notifications
You must be signed in to change notification settings - Fork 209
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
Provide parameters interactively [Feature Request] #793
Comments
This seems similar to #833 in objective. Is that true? |
Woops, hit close by mistake :) @squillace yes, the objectives are similar; this was opened back in November, #833 more recently. I think the only material difference is that #833 also describes saving the inputs in a "parameters file" that porter then uses, whereas my issue describes forwarding the values straight to porter without persisting them to disk - I do like the idea of a "parameters file" though. |
A related update here. Although not necessarily fulfilling the request in this ticket, Porter has now introduced structured parameter mappings aka Parameter Sets. These can currently be generated interactively, similar to credentials generation, e.g. |
We have since moved away from interactive commands (#1080). I recommend that we use different UI than porter's CLI (such as VS Code) to improve upon the interactive/discoverable experience. |
Problem
Some apps have a lot of configurable parameters, which can be fiddly to supply using the
porter install --param/param-file
syntax. Additionally, having to supply several parameters on the command line can be a bit daunting for some users who are less Linux-savvy.Request
In addition to the existing
--param/param-file
syntax, this request is for the possibility to supply parameter values interactively.There would need to be a means of entering interactive mode, such as:
porter install --interactive
or in short formporter install -i
Ideally this could be combined with the existing
--param/param-file
syntax, which would provide default values that could be changed interactively if required (or perhaps suppress those prompts).Worked Example
Consider the following porter YAML snippet:
The following command is issued:
The interactive prompts begin:
Here the value is defaulted from the value provided on the command line, and can be adjusted if required.
Here the value is defaulted from the YAML config, and can be adjusted if required.
The text was updated successfully, but these errors were encountered: