You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In all cases, using the interactive TUI should be optional, and backward-compatible. If you're invoking ko build or ko resolve with flags today today, you should be able to keep doing that and never see an interactive UI.
But, if you don't, we can guide you through the necessary options.
Some possible examples:
If you haven't set KO_DOCKER_REPO, instead of failing, prompt for it. We can also ask if you want to persist this for future calls.
If you ko resolve without specifying a filepath, we can prompt you for one, and maybe autocomplete based on what directories exist and contain YAML files. (Maybe we could just do this with cobra though? 🤔)
Since build: Imply current import path #717 we accept a bare ko build, so we can't prompt to select an importpath, but maybe if you ko build <tab> we can intercept that and figure out which importpaths exist in the current context and let you choose one. Maybe with type-ahead autocomplete if there are more than a few of them.
There's probably more.
I'd also like to optionally have a better UX for pushing images, with grouped progress bars instead of the current interleaved logging. I'm imagining something like:
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.
We can use bubbletea from https://charm.sh to give a layer of paint to our CLI.
In all cases, using the interactive TUI should be optional, and backward-compatible. If you're invoking
ko build
orko resolve
with flags today today, you should be able to keep doing that and never see an interactive UI.But, if you don't, we can guide you through the necessary options.
Some possible examples:
KO_DOCKER_REPO
, instead of failing, prompt for it. We can also ask if you want to persist this for future calls.ko resolve
without specifying a filepath, we can prompt you for one, and maybe autocomplete based on what directories exist and contain YAML files. (Maybe we could just do this with cobra though? 🤔)ko build
, so we can't prompt to select an importpath, but maybe if youko build <tab>
we can intercept that and figure out which importpaths exist in the current context and let you choose one. Maybe with type-ahead autocomplete if there are more than a few of them.There's probably more.
I'd also like to optionally have a better UX for pushing images, with grouped progress bars instead of the current interleaved logging. I'm imagining something like:
We can fallback to printing out layer digests if it's not a terminal, or if you opt out. (or don't opt in).
Ideas and feedback welcome, including any feedback that you don't want this. 😄
The text was updated successfully, but these errors were encountered: