Closed spuder closed 3 years ago
Workaround is to set this on every resource
resource "artifactory_remote_repository" "docker-remote" {
key = "docker-remote"
package_type = "docker"
repo_layout_ref = "simple-default"
url = "https://registry-1.docker.io/"
notes = "managed by terraform"
content_synchronisation {
enabled = null
}
}
FYI - I hit issues with setting to 'null', but using 'false' works cleanly.
I am unable to recreate this issue - and, more importantly: is it an issue? Or, is it just not what you expected?
Ran into this again today. If we omit content_synchronization
then we are unable to import any manually created resources from artifactory into terraform.
If we include content_synchronization
the first time a resources is created with TF, then it fails with rpc transport is closing
.
So we are stuck in this very tricky pattern where we have to omit content_synchronization
on the very first terraform apply, but then we have to add it in for the second terraform apply, unless we are importing a resource.
Ok, thanks. Let me dig into this. Not sure How much priority I can give this - if you're a paying customer, filing a support ticket will light a fire thought :)
@spuder - Can you clarify with me what behavior you would like to see? And, I simply can't repo it - so, I need something (ideally) copy-and-pastable.
Terraform 0.13.0 Module 2.2.4 Artifactory 6.23
When importing a remote resource from artifactory, it wants to set a value named
content_synchronisation
, but that does not appear to be a valid resource parameterterraform import artifactory_remote_repository.conan-remote conan-remote
terraform apply
https://registry.terraform.io/providers/jfrog/artifactory/latest/docs/resources/artifactory_remote_repository#synchronize_properties