Skip to content
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

Error executing command: unable to generate website: unexpected error: openpgp: signature made by unknown entity #217

Closed
dineshhg opened this issue Feb 3, 2023 · 2 comments

Comments

@dineshhg
Copy link

dineshhg commented Feb 3, 2023

0.4.0 Release is not working anymore

Error executing command: unable to generate website: unexpected error: openpgp: signature made by unknown entity

tempsnip

I'm not able to find any resource saying that the 0.4.0 version will stop working going forward.


Solution: Upgrade to the latest 0.13.0

@dineshhg dineshhg changed the title 0.4.0 Release is not working anymore Error executing command: unable to generate website: unexpected error: openpgp: signature made by unknown entity Feb 3, 2023
@bflad
Copy link
Member

bflad commented Dec 21, 2023

Hi @dineshhg 👋 Thank you for reporting this and sorry you ran into trouble here.

What I suspect happened here was part of https://discuss.hashicorp.com/t/terraform-updates-for-hcsec-2021-12/23570, where new Terraform patch releases were created due to a security concern. The terraform-plugin-docs generate command relies on calling Terraform CLI to get the documentation out of the provider except when the recent -provider-schema flag is used. If the terraform-plugin-docs project was to introduce any breaking changes, they would be announced in the changelog and release notes, but in this case it was a Terraform CLI issue so there was no announcement. I think the best thing in this case was to do exactly what you did, raise a GitHub bug report here.

Since there is nothing actionable here, except potentially making the error messaging clear about the issue being with Terraform CLI (already covered by #136), I'm going to close this issue. We do really appreciate the report and solution though -- it likely helped others.

@bflad bflad closed this as completed Dec 21, 2023
Copy link

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants