Base package for container registry operations. This package provides the registry command namespace that provider packages extend with their own subcommands.
Provider packages (such as community/registry-aws or community/registry-docker) depend on this package and add commands under the registry profile to integrate with specific container registries.
aux4 aux4 pkger install aux4/registry
You also need to install at least one provider package to use registry commands:
aux4 aux4 pkger install community/registry-aws
aux4 aux4 pkger install community/registry-docker
This package defines the registry command group with an empty profile. Provider packages add their commands to the registry profile, creating a unified command structure:
aux4 registry <provider> <command>
For example:
aux4 registry aws login
aux4 registry aws push --image my-app:latest
aux4 registry docker login --registry ghcr.io
aux4 registry docker push --image my-app:latest
| Provider | Package | Registry | |----------|---------|----------| | aws | community/registry-aws | Amazon ECR | | docker | community/registry-docker | Docker Hub, GHCR, and other OCI registries |
A registry provider is a standard aux4 package that adds commands under the registry profile. The package must:
aux4/registry as a dependencyregistry tagregistry profile using the provider name (e.g., aws, docker, gcp, azure)registry:<provider> profile containing the provider's subcommandslogin and pushEvery registry provider should implement the following commands:
Authenticates with the container registry.
aux4 registry <provider> login [--registry <url>]
Pushes a container image to the registry.
aux4 registry <provider> push --image <name:tag> [--registry <url>]
See the community/registry-aws or community/registry-docker packages for complete provider implementation examples.