Alper Rifat Ulucinar

Thanks @muvaf. To have cross references with some existing issues and for further discussion: - https://github.com/crossplane/terrajet/issues/264 - https://github.com/crossplane/terrajet/issues/158#issuecomment-1205292185

For some providers, Terraform registry has consistent "import statement" documentation (which we used to determine most group names for resources). One idea could be to use that metadata for automatically...

Hi @displague, Could you please try overriding the default value of the `--prelude-xpath` command-line argument in [`apis/generate.go`](https://github.com/crossplane-contrib/provider-jet-equinix/blob/97eb823e70fd751ff0265128a6db4dfbad9d8909/apis/generate.go#L34) with something like: ```go //go:generate go run github.com/upbound/upjet/cmd/scraper -n ${TERRAFORM_PROVIDER_SOURCE} -r ../.work/${TERRAFORM_PROVIDER_SOURCE}/${TERRAFORM_DOCS_PATH} -o...

Hi @displague, We had a recent change in the scraper that was motivated by fixing a case in upbound/provider-gcp. I don't expect it to address the duplication or the wrong-section...

Hi @arfevrier, Thank you for reporting these issues. I also agree your concerns about the lack of progress logs in the non-debug log level of the provider. Regarding tracking potentially...

Hi @arfevrier, Thank you for the detailed analysis & reports. I see the following messages in the logs related to the `benchmarksix10` resource: ``` "2023-10-11T15:48:59Z\tDEBUG\tprovider-gcp\tSuccessfully deleted managed resource\t{\"controller\": \"managed/dns.gcp.upbound.io/v1beta1, kind=recordset\",...

Hi @dougsong, Per the Crossplane resource model, the source of truth for the external resource's name is the external-name annotation: https://github.com/crossplane/crossplane/blob/master/design/one-pager-managed-resource-api-design.md#external-resource-name We may fix the diagram if it's confusing. The...

Hi folks, The template provider does not use the shared gRPC server and instead, relies on the Terraform CLI to manage the lifecycle of the native provider process. Thus, we...

We had also better revisit the hardcoded repo root [here](https://github.com/upbound/upjet-provider-template/blob/05c03f0f6ab6d1c2083098f6516651b55bbae648/cluster/images/upjet-provider-template/Dockerfile#L28) and expose it as a Make variable so that it will be easier for folks to utilize other download locations...

Added the `enhancement` label to reflect the Dockerfile & Makefile changes.