-
Notifications
You must be signed in to change notification settings - Fork 38
Figure out how to get CRD documentation from Terraform #92
Comments
It seems like in some cases we do have this - I just noticed provider-jet-gcp seems to. Is this because they fill the On a related note, I was coming here to report that sometimes this commentary is misleading. For example at: https://doc.crds.dev/github.com/crossplane-contrib/provider-jet-gcp/cloudplatform.gcp.jet.crossplane.io/Project/[email protected]
I don't think we'll actually recreate a new project as this documentation states. |
Just came across this issue and I think I've found where terraform documentation for provider resources are coming from: All content seems to be living as markdown files under https://github.com/hashicorp/terraform-provider-aws/tree/main/website/docs For example, documentation for aws_instance is here: https://github.com/hashicorp/terraform-provider-aws/blob/main/website/docs/r/instance.html.markdown |
@negz Yes, that's the case. GCP fills
Here is the fix crossplane-contrib/provider-jet-gcp#10 |
A relevant proposal's reference: crossplane/crossplane#2956 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
What problem are you facing?
Currently fields don't have any documentation since most of TF providers do not fill
Description
field of theSchema
objects.How could Terrajet help solve your problem?
We should investigate how https://registry.terraform.io/providers/hashicorp/aws/latest/docs and other docs are produced and see how we can add description comments to generated fields.
The text was updated successfully, but these errors were encountered: