Skip to content
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.

Kaiser login command is confusing #22

Open
Metallion opened this issue Sep 11, 2019 · 0 comments
Open

Kaiser login command is confusing #22

Metallion opened this issue Sep 11, 2019 · 0 comments

Comments

@Metallion
Copy link
Member

I think the most natural expectation for a command named kaiser login is to get a shell on a container. It however just executes a command and to get the shell you have to run kaiser login sh.

I believe it's better to split this into two commands:

  • kaiser exec to run commands.
  • kaiser login to get a shell. This would be equivalent to running kaiser exec sh

While we're at it, we might want to add a parameter to specify which container we want to do this against. Currently it's hard coded to the app container and I this should remain the default but perhaps a parameter like the following is a good idea?

kaiser exec uptime #runs uptime on the app container
kaiser exec -c db uptime #runs uptime on the db container
kaiser login # gets us a shell on the app container
kaiser login -c db #gets us a shell on the db container
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant