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

Missing URN attribute in digitalocean_container_registry #1238

Open
adam-kulagowski opened this issue Oct 3, 2024 · 2 comments
Open

Missing URN attribute in digitalocean_container_registry #1238

adam-kulagowski opened this issue Oct 3, 2024 · 2 comments
Labels
do-api Depends on changes to the DigitalOcean API

Comments

@adam-kulagowski
Copy link

adam-kulagowski commented Oct 3, 2024

Is your feature request related to a problem? Please describe.

I'm trying to attach Container registry to my project using OpenTofu. However it looks like that digitalocean_project_resources requires URN id in order to attach it to selected project.

In terms of code:

# Create docker registry
resource "digitalocean_container_registry" "XXX_registry" {
  name                   = "XXX-registry"
  subscription_tier_slug = "basic"
}

# Assign registry to XXX project
resource "digitalocean_project_resources" "registry" {
  project = digitalocean_project.XXX.id
  resources = [ digitalocean_container_registry.XXX_registry.urn ]
}

Which ends up w/ error that there is no URN attribute for digitalocean_container_registry and quick documentation search confirms it.

Describe the solution you'd like

digitalocean_container_registry should have URN attribute as other Digital Ocean resources.

Describe alternatives you've considered

In terms of TF: None as my TF skills are pretty limited :)
Others: Using UI which suggests that Container Registry cannot by assigned to a project?

Additional context

I'm using 2.42.0 release
I would be happy with any TF workaround.

@andrewsomething andrewsomething added the do-api Depends on changes to the DigitalOcean API label Oct 3, 2024
@andrewsomething
Copy link
Member

Others: Using UI which suggests that Container Registry cannot by assigned to a project?

That's correct. This is currently a product limitation. A Container Registry cannot be assigned to a project at this time. When that changes, we'll be sure to support it here in Terraform.

@adam-kulagowski
Copy link
Author

Ah, that explains it. Thanks for the clarification :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-api Depends on changes to the DigitalOcean API
Projects
None yet
Development

No branches or pull requests

2 participants