Is there an existing issue for this?
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
Description
Since Nexus 3.83.0, Path based routing is the preferred and default connector for Docker repositories.
This means that, in the UI, this option is selected by default. However, when using the API to get a docker repository, this option is set to "null". This breaks connections to these types of repositories. Manually re-enabling path-based routing works as a temporary solution until Terraform updates the repositories, resetting this option back to null while it still shows as enabled in the UI.
New or Affected Resource(s)/Data Source(s)
nexus_repository_docker_hosted, nexus_repository_docker_proxy, nexus_repository_docker_group
Pro feature
Community Plugin
No response
Potential Terraform Configuration
resource "nexus_repository_docker_hosted" "example" {
docker {
path_based_routing = true
}
}
References
No response
Is there an existing issue for this?
Community Note
Description
Since Nexus 3.83.0, Path based routing is the preferred and default connector for Docker repositories.
This means that, in the UI, this option is selected by default. However, when using the API to get a docker repository, this option is set to "null". This breaks connections to these types of repositories. Manually re-enabling path-based routing works as a temporary solution until Terraform updates the repositories, resetting this option back to null while it still shows as enabled in the UI.
New or Affected Resource(s)/Data Source(s)
nexus_repository_docker_hosted, nexus_repository_docker_proxy, nexus_repository_docker_group
Pro feature
Community Plugin
No response
Potential Terraform Configuration
References
No response