Skip to content
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

Improve Creating Project flow. #12

Closed
Vad1mo opened this issue Feb 6, 2024 · 2 comments · Fixed by #73
Closed

Improve Creating Project flow. #12

Vad1mo opened this issue Feb 6, 2024 · 2 comments · Fixed by #73

Comments

@Vad1mo
Copy link
Member

Vad1mo commented Feb 6, 2024

When creating a project as a user, I would expect that there is no need to explicitly provide the --name parameter.

So something like this ./harbor create project vadim-test should work.
--public should be by default `false``
The description and logic behind --registry-id int is not obvious/clear. When id !=1 does it mean that than a proxy project is created?
./harbor create project vadim-test
Error: [POST /projects][500] createProjectInternalServerError &{Errors:[0x14000130020]}
Usage:
harbor create project [flags]

Flags:
-h, --help help for project
--name string Name of the project
--public Project is public or private (default true)
--registry-id int ID of referenced registry when creating the proxy cache project (default 1)
--storage-limit int Storage quota of the project (default -1)

@amands98
Copy link
Collaborator

fixed by #35

@bupd
Copy link
Collaborator

bupd commented May 24, 2024

The #35 is missing these conditions as per this issue definition:

So something like this ./harbor create project vadim-test should work.
--public should be by default `false``

The ./harbor project create [project name] does not work, since the create command is not accepting any argument.

and the --public flag defaults to true. which should be fixed.

Any thoughts..??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants