RegistryRepository is the Schema for the RegistryRepositorys API. A repository for storing artifacts
Type
CRD
Group
artifact.gcp.upbound.io
Version
v1beta1
apiVersion: artifact.gcp.upbound.io/v1beta1
kind: RegistryRepository
RegistryRepositorySpec defines the desired state of RegistryRepository
No description provided.
Cleanup policies for this repository. Cleanup policies indicate when certain package versions can be automatically deleted. Map keys are policy IDs supplied by users during policy creation. They must unique within a repository and be under 128 characters in length. Structure is documented below.
Policy condition for matching versions. Structure is documented below.
Match versions by package prefix. Applied on any prefix match.
Match versions by tag prefix. Applied on any prefix match.
Match versions by version name prefix. Applied on any prefix match.
Policy condition for retaining a minimum number of versions. May only be specified with a Keep action. Structure is documented below.
Match versions by package prefix. Applied on any prefix match.
Docker repository config contains repository level configuration for the repositories of docker type. Structure is documented below.
MavenRepositoryConfig is maven related repository details. Provides additional configuration details for repositories of the maven format type. Structure is documented below.
Configuration specific for a Remote Repository. Structure is documented below.
Specific settings for an Apt remote repository. Structure is documented below.
One of the publicly available Yum repositories supported by Artifact Registry. Structure is documented below.
Specific settings for a Docker remote repository. Structure is documented below.
Specific settings for a Maven remote repository. Structure is documented below.
Specific settings for an Npm remote repository. Structure is documented below.
Specific settings for a Python remote repository. Structure is documented below.
The credentials used to access the remote repository. Structure is documented below.
Use username and password to access the remote repository. Structure is documented below.
Reference to a SecretVersion in secretmanager to populate passwordSecretVersion.
Policies for referencing.
Selector for a SecretVersion in secretmanager to populate passwordSecretVersion.
Policies for selection.
Specific settings for an Yum remote repository. Structure is documented below.
One of the publicly available Yum repositories supported by Artifact Registry. Structure is documented below.
Configuration specific for a Virtual Repository. Structure is documented below.
Policies that configure the upstream artifacts distributed by the Virtual Repository. Upstream policies cannot be set on a standard repository. Structure is documented below.
Reference to a RegistryRepository in artifact to populate repository.
Policies for referencing.
Selector for a RegistryRepository in artifact to populate repository.
Policies for selection.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Cleanup policies for this repository. Cleanup policies indicate when certain package versions can be automatically deleted. Map keys are policy IDs supplied by users during policy creation. They must unique within a repository and be under 128 characters in length. Structure is documented below.
Policy condition for matching versions. Structure is documented below.
Match versions by package prefix. Applied on any prefix match.
Match versions by tag prefix. Applied on any prefix match.
Match versions by version name prefix. Applied on any prefix match.
Policy condition for retaining a minimum number of versions. May only be specified with a Keep action. Structure is documented below.
Match versions by package prefix. Applied on any prefix match.
Docker repository config contains repository level configuration for the repositories of docker type. Structure is documented below.
MavenRepositoryConfig is maven related repository details. Provides additional configuration details for repositories of the maven format type. Structure is documented below.
Configuration specific for a Remote Repository. Structure is documented below.
Specific settings for an Apt remote repository. Structure is documented below.
One of the publicly available Yum repositories supported by Artifact Registry. Structure is documented below.
Specific settings for a Docker remote repository. Structure is documented below.
Specific settings for a Maven remote repository. Structure is documented below.
Specific settings for an Npm remote repository. Structure is documented below.
Specific settings for a Python remote repository. Structure is documented below.
The credentials used to access the remote repository. Structure is documented below.
Use username and password to access the remote repository. Structure is documented below.
Reference to a SecretVersion in secretmanager to populate passwordSecretVersion.
Policies for referencing.
Selector for a SecretVersion in secretmanager to populate passwordSecretVersion.
Policies for selection.
Specific settings for an Yum remote repository. Structure is documented below.
One of the publicly available Yum repositories supported by Artifact Registry. Structure is documented below.
Configuration specific for a Virtual Repository. Structure is documented below.
Policies that configure the upstream artifacts distributed by the Virtual Repository. Upstream policies cannot be set on a standard repository. Structure is documented below.
Reference to a RegistryRepository in artifact to populate repository.
Policies for referencing.
Selector for a RegistryRepository in artifact to populate repository.
Policies for selection.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
RegistryRepositoryStatus defines the observed state of RegistryRepository.
No description provided.
Cleanup policies for this repository. Cleanup policies indicate when certain package versions can be automatically deleted. Map keys are policy IDs supplied by users during policy creation. They must unique within a repository and be under 128 characters in length. Structure is documented below.
Policy condition for matching versions. Structure is documented below.
Match versions by package prefix. Applied on any prefix match.
Match versions by tag prefix. Applied on any prefix match.
Match versions by version name prefix. Applied on any prefix match.
Policy condition for retaining a minimum number of versions. May only be specified with a Keep action. Structure is documented below.
Match versions by package prefix. Applied on any prefix match.
Docker repository config contains repository level configuration for the repositories of docker type. Structure is documented below.
MavenRepositoryConfig is maven related repository details. Provides additional configuration details for repositories of the maven format type. Structure is documented below.
Configuration specific for a Remote Repository. Structure is documented below.
Specific settings for an Apt remote repository. Structure is documented below.
One of the publicly available Yum repositories supported by Artifact Registry. Structure is documented below.
Specific settings for a Docker remote repository. Structure is documented below.
Specific settings for a Maven remote repository. Structure is documented below.
Specific settings for an Npm remote repository. Structure is documented below.
Specific settings for a Python remote repository. Structure is documented below.
The credentials used to access the remote repository. Structure is documented below.
Use username and password to access the remote repository. Structure is documented below.
Specific settings for an Yum remote repository. Structure is documented below.
One of the publicly available Yum repositories supported by Artifact Registry. Structure is documented below.
Configuration specific for a Virtual Repository. Structure is documented below.
Policies that configure the upstream artifacts distributed by the Virtual Repository. Upstream policies cannot be set on a standard repository. Structure is documented below.
Conditions of the resource.
my-repo
apiVersion: artifact.gcp.upbound.io/v1beta1
kind: RegistryRepository
metadata:
annotations:
meta.upbound.io/example-id: artifact/v1beta1/registryrepository
labels:
testing.upbound.io/example-name: my-repo
name: my-repo
spec:
forProvider:
description: example docker repository
format: DOCKER
location: us-central1
my-repo
apiVersion: artifact.gcp.upbound.io/v1beta1
kind: RegistryRepository
metadata:
annotations:
meta.upbound.io/example-id: artifact/v1beta1/registryrepositoryiammember
uptest.upbound.io/pre-delete-hook: testhooks/delete-registryrepositoryiammember.sh
labels:
testing.upbound.io/example-name: my-repo
name: my-repo
spec:
forProvider:
description: example docker repository
format: DOCKER
location: us-central1
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.