Skip Loginview create when credentials already exist

[qcserestipy]

Fixes #267

Check for Existing Credentials and Bypass Login View Creation

1. Implemented a verification step to detect existing Harbor credentials in the current configuration.
2. If valid credentials are found, the creation of a new login view is skipped.
3. Enhances login efficiency by reusing stored credentials and reducing unnecessary prompts.

ToDo: Add base64 encoding for password in config file?

[qcserestipy]

To resolve the failing tests I will introduce a mock Keyring since the container has no keyring.

[bupd]

There should be an easy way to change the login credentials directly.

• Changing login credentials should not need users to change the config.yaml

[qcserestipy]

@bupd Do you thing it would come in handy to create a config subcommand that lets us manipulate the config file?
Such that a user could do something like harbor config set Credential.Password <password> to update a field in the config file. In case not what do you think would be a better idea?

[bupd]

Yes this one's good. Should be able to get and set the config without touching the config file.

Also it would be great if we could set the current-credential name in config from CLI

[qcserestipy]

@bupd I added the config sub command and several tests for its functionality. I added some screenshots:

Listing Config Items and Setting them

Clearing config items

Retrieving config items

Setting credentials and credentialname supported with --name flag

[qcserestipy]

@bupd There is still a sign off error in one of the commits. Unfortunately, I would have to rebase over 34 commits from main. Is there an easier way to do this?

[bupd]

Try squashing the commits

[bupd]

@qcserestipy did you also add changing between different login accounts via changing the credential name command.

Which utilizes the current credential name.

[qcserestipy]

@bupd I went through the rebase and it worked with a little bit of manual work.
Concerning your second question can you give me an example what you mean?

You can set the current-credential-name with the command too:

[Standing-Man]

Hi @qcserestipy and @bupd, If the command format is as follows, it might be even better.

• harbor context list -> list all context
• harbor context create -> create a new context for now
• harbor context view -> view current context
• harbor context delete -> delete context
• ....

This is just a suggestion I have for this command. I'm not sure if it would be more user-friendly, but I’d love to hear your thoughts!

[qcserestipy]

@bupd @Standing-Man I think a discussion about the context command would be interesting. However, I think than we would have to narrow down the reason for each of the commands. When I was working on the config settings recently and introduced I already thought that the login command also takes over some of those responsibilities. In case we use context and config what is the reason for login? I also added a small part when a user uses login with new credentials or updates credentials the current cred name is also automatically updated. In this way users could use the login command to manage credentials or the config command.

What is your opinion on this all? To me it is not 100% clear right now which command should take over which functionality since there is a little bit overlap right now.