Add proposal for official CLI project for Harbor #220
Conversation
akshatdalton
force-pushed
the
proposal/cli
branch
3 times, most recently
from
97e5b8a
to
559fd81
Compare
proposals/new/cli.md
Outdated
| } | ||
|
|
||
| jsonStr := JsonMarshallWithMultipleTypes(response) | ||
| fmt.Println(jsonStr) |
There was a problem hiding this comment.
Later we can improve the way we show the response, in this case, we can show it in the tabular form.
|
looks good so far :) |
|
@Vad1mo @wy65701436 can you take a look please :) |
akshatdalton
force-pushed
the
proposal/cli
branch
from
559fd81
to
aba26cb
Compare
akshatdalton
force-pushed
the
proposal/cli
branch
from
aba26cb
to
d4f27d6
Compare
Signed-off-by: Akshat <[email protected]>
akshatdalton
force-pushed
the
proposal/cli
branch
from
d4f27d6
to
7392a8e
Compare
|
I'm adding my 2 centes about this proposal. I think having an official CLI to be able to manipulate harbor is more than necessary at the moment :-). A CLI that allows you to do the same thing as the API. I don't know much about the process to ensure that there is an official CLI for Harbor but I think that several people, a community, could work on the subject. And as we know, the most difficult thing is not to create a CLI but to ensure that it remains up to date when the API is also updated and that it follows the same release cycle as the project core. So my question is, is it planned to have several people working on the subject or only one person should make a proposal with an existing CLI? |
No description provided.