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

move OCI/Docker-registry-related cmds from remote to their own cmd #1908

Conversation

preminger
Copy link
Contributor

Description of the Pull Request (PR):

Moves the operations associated with OCI/Docker registries - login, logout, and list - from subcommands of the remote command (singularity remote login [options] <registryURI>, etc.) to their own dedicated command, registry (singularity registry login [options] <registryURI>, etc.). See the output of singularity help registry for more information.

Note that this does not remove the subcommands login, logout, and list from singularity remote, as they have separate functionality when given a remote endpoint (Singularity Cloud Services, Singularity Enterprise installs) as an argument. This former "duality" of functions of singularity remote {login, logout, list} is in fact a central part of the motivation for this PR. (See #1639 for discussion.) See the output of singularity help remote for more information.

This fixes or addresses the following GitHub issues:

@preminger preminger added the enhancement New feature or request label Jul 18, 2023
@preminger preminger added this to the SingularityCE 4.0.0 milestone Jul 18, 2023
@preminger preminger force-pushed the 1894-move-oci-registry-operations-from-remote-to-new-registry-command branch 2 times, most recently from d72dfc8 to a8d8fb8 Compare July 20, 2023 19:32
@preminger preminger changed the title WIP: move OCI/Docker-registry-related cmds from remote to their own cmd move OCI/Docker-registry-related cmds from remote to their own cmd Jul 20, 2023
@preminger preminger requested a review from dtrudg July 20, 2023 19:43
Copy link
Member

@dtrudg dtrudg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The registry specific changes here LGTM.

Should be good to go after #1905 is completed.

@preminger preminger force-pushed the 1894-move-oci-registry-operations-from-remote-to-new-registry-command branch 2 times, most recently from d0c4010 to 9c43892 Compare July 21, 2023 14:18
@preminger preminger marked this pull request as ready for review July 21, 2023 15:03
@preminger preminger force-pushed the 1894-move-oci-registry-operations-from-remote-to-new-registry-command branch 2 times, most recently from b4c409d to 228f623 Compare July 21, 2023 15:26
@preminger preminger force-pushed the 1894-move-oci-registry-operations-from-remote-to-new-registry-command branch from 228f623 to eee3372 Compare July 21, 2023 15:29
@preminger preminger requested a review from dtrudg July 21, 2023 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

move OCI registry operations from remote to new registry command
2 participants