Reworking the remote Command about singularity HOT 3 CLOSED

@preminger - as a relative newcomer, it'd be great if you would be able to consider the design of the singularity remote command.

At present, it is massively overloaded in a way that is confusing. It handles...

• Configuring, logging in to, switching between remote endpoints, where a remote endpoint is a Singularity Cloud Services URI, or a Singularity Enterprise install. Each remote endpoint offers a range of services (library/builder/keystore).
• Logging into / out of OCI registries, to pull private docker:// or oras:// containers.
• Configuring separate standalone PGP keyserver, which are not part of a remote endpoint.
• Concepts of 'global' and 'exclusive' or 'ordered' endpoints / keyservers. Where the administrator can influence which is used.

We need to take a really hard look at:

• What do we think remote should / shouldn't do? Is there any functionality that should be moved to another command, or removed entirely?
• What's confusing about the active / global / exclusive stuff? Is it really necessary? Can it be presented better?

It'd be fantastic if you could...

• Absorb the current documentation.
• Try out the functionality it describes.
• Note what's confusing / doesn't work.
• Share any thoughts on how you think 'endpoints', keyservers, OCI logins could be presented.

from singularity.

Opened Discussions topic on this, at #1639

from singularity.

Closing - see #1639 (comment) for details.

from singularity.