New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Generation with version v0.19.0 removes links and bulletpoints #355
Comments
We also face this problem in aiven/terraform-provider-aiven#1694. There is also another problem that we have. I'll create a new issue for it, too. |
Hi @lechnerc77, Currently, the Terraform public registry doesn't ingress the Either way, if you are only using the |
Hi @SBGoods , thanks for your quick support and your explanation. Then I will regenerate the documentation with the latest version. As the description field is anyway not of relevance as of today, The look of the content is okay for me. Maybe we have to adjust the layout then at some later point in time if the Terraform registry considers that part of the markdown. Maybe it would be worth to add this change in PR #332 to the release notes of 0.19.0 to avoid questions like mine. From my perspective this issue can be closed then. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform CLI and terraform-plugin-docs Versions
Terraform version: 1.7.3
terraform-plugin-docs: 0.19.0
Provider Code
Expected Behavior
With the update from version 0.18.0 to 0.19.0 there are no changes in the generated markdown
Actual Behavior
The markdown gets reformated (bullet points are removed without proper spacing) as well as links are removed
Steps to Reproduce
How much impact is this issue causing?
Medium
Logs
No response
Additional Information
Here some screenshots that highlight the mismatch between the versions:
The template that is used
The schema of the resource with the desscriptions
The Git diff between version 0.18.0 and 0.19.0
Code of Conduct
The text was updated successfully, but these errors were encountered: