Alex Hung

@jmvitali I have not been able to reproduce this issue by creating the Docker v2 repo itself. However, this may be a timing issue as suggested in [this post](https://discuss.hashicorp.com/t/root-resource-was-present-but-now-absent-in-terraform/34047/10). The...

@jmvitali Quick question: are you using provider alias? i.e. `provider = artifactory.foo` in your resource? I wonder if this is related to #892

@jmvitali Perhaps it isn't possible in your setup/configuration, the use of [resource references](https://developer.hashicorp.com/terraform/language/expressions/references#references-to-resource-attributes) or [depends_on](https://developer.hashicorp.com/terraform/language/meta-arguments/depends_on) meta argument will help Terraform figures out the dependencies between resources and sequence them correctly....

@jmvitali Can you give [v10.3.2](https://registry.terraform.io/providers/jfrog/artifactory/10.3.2) (or later) a try and let me know if the problem still exists?

@ssyeds There're 2 steps in starting to manage existing infrastructure: 1. Create the Terraform configuration to match the infrastructure. This can be time consuming for large number of resources. 2....

@chb0github The new [`import` block](https://developer.hashicorp.com/terraform/language/import) does half of the job already with the ability to generate the HCL from IDs. We can help with the remaining part and query JFrog...

@chb0github I envision this tool will have ability to let user specify the 'category' to extract, e.g. local/remote/virtual/federated repos, security, configuration, etc. as well as specific resource type `artifactory_permission_target`. Probably...

@chb0github 😄 Now try this on an instance with 5000+ repos. And you must not DDoS the instance.

> You know, I actually thought about this: technically you don't need terra form import: you can just interrogate all the resources yourself and generate the proper HCl That's the...

@chb0github You should consider creating a public repo with these scripts 😄