unikubehq
restrict deck list to "upped" project
Not sure if I got it wrong - however, I feel like the choices for the deck install command are a bit too "loose". Basically it offers me all deck's (even from other projects). Wouldn't it make more sense to display only the decks of the "upped" project / the decks which actually belong the the currently running cluster?
@Schille @buschNT
I think it is fine. Once issue #161 is solved and the context works as expected, deck install should almost never show all decks available. The command would consider the context in the unikube.yaml of the project you are currently working on. Maybe at this point it would be to restrictive.
@SteinRobert I guess you do not have any context set.
Correct, I did not have any context set.
Once issue #161 is solved and the context works as expected, deck install should almost never show all decks available.
In most of the situations I'm using deck install (often just updating charts or an app) there is no unikube.yaml in the current directory..
Since the cli only supports one "upped" cluster at a time I feel like the given project could be set to the context implicitly, couldn't it?
Since the cli only supports one "upped" cluster at a time I feel like the given project could be set to the context implicitly, couldn't it?
Yes we could, but then the deck install command would not always result in the same outcome. This could be confusing when writing scripts. I would recommend to add a "unikube.yaml", once #161 is fixed.
So I am not sure if the implicit context would help or confuse :/
Yes we could, but then the deck install command would not always result in the same outcome. This could be confusing when writing scripts.
But that isn't the case anyway, right? When the project (helm charts) gets updated or something changes on the platform the choices of the command will likely differ as well.
I would recommend to add a "unikube.yaml", once #161 is fixed.
I believe this is not a proper solution. That means I would need to write a unikube.yaml file, just to set a project context. That's a bit of a hassle. Rather I'd recommend creating a unikube.yaml when writing scripts.