gdcloud artifacts push

NAME

gdcloud artifacts push - Push OCI packages to a registry.

SYNOPSIS

gdcloud artifacts push SOURCE DESTINATION [flags]

EXAMPLES

To push a OCI packages to a registry, run:

            gdcloud artifacts push SOURCE DESTINATION

        To push a single manifest of the repository to the registry, run:

            gdcloud artifacts push SOURCE DESTINATION --single-manifest-repo

        To push OCI packages to a registry without adhering to TLS protocols, run:

            gdcloud artifacts push SOURCE DESTINATION --insecure

        The SOURCE path must point to a directory containing the OCI bundle.
        The DESTINATION is a reference of a remote OCI image. For example, gcr.io/cloud-marketplace/google/nginx:1.25.
        This command writes the extracted image to the output path specified in SOURCE. This output path must point to an empty directory.

OPTIONAL FLAGS

      --ca-cert-path string    Absolute file path to the user-provided CA certificate file that is used to push a manifest over a HTTPS connection.
      --insecure               Allow pushing to the registry, and establish a connection to the server, even for server connections otherwise considered insecure.
      --single-manifest-repo   Tag and push the single manifest of the repository, as opposed to the image index, to the registry.

GDCLOUD WIDE FLAGS

These flags are available to all commands: --configuration, --format, --help, --project, --quiet.

For more information, see the gdcloud CLI reference overview page.