Skip to content

Add support for custom upstream docker registries in google_artifact_registry_repository #2110

Open
@rail

Description

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave +1 or me too comments; they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  • If the issue is assigned to a user, that user is claiming responsibility for the issue.

Description

The docker_repository.public_repository section of google_artifact_registry_repository supports DOCKER_HUB only, see https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/artifact_registry_repository#nested_docker_repository and https://github.com/hashicorp/terraform-provider-google/blob/1ba50ab27d4185c49a77ede83e665d1152fa6860/google/services/artifactregistry/resource_artifact_registry_repository.go#L361

Google supports custom registries. For example, you can specify "https://quay.io" and get it worked.

It would be great to allow arbitrary upstream registries.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions