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

Circular, empty reference in provisioner documentation #12898

Closed
anEXPer opened this issue Mar 21, 2024 · 1 comment · Fixed by #13042
Closed

Circular, empty reference in provisioner documentation #12898

anEXPer opened this issue Mar 21, 2024 · 1 comment · Fixed by #13042
Labels
bug docs stage/accepted Confirmed, and intend to work on. No timeline commitment though.

Comments

@anEXPer
Copy link

anEXPer commented Mar 21, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Overview of the Issue

The documentation describing provisioners contains a loop of references between two doc locations,
neither of which delivers the information the link to it claims.

The hcl_templates docs claim that the list of available provisioners can be found in the provisioners section.

Following that link, the main provisioners docs do not list available provisioners, instead listing use-cases you may want to use them for. It then links back to the prior page, with the claim The documentation includes details about each type of provisioner.

The only thing on that page I could identify as a "type of provisioner" is On Error Provisioner and it does not appear to be part of a set.

My initial impulse is to remove the claims that the documentation makes about the information that will be found in each article, while maintaining the link itself. But, it would be even better if the promised list of available provisioners and details about each type of provisioner were made clearly available; unfortunately, I don't yet know how to do that.

Do such resources currently exist somewhere in the documentation?
Did they previously?

Should I just excise the falsehoods in a PR?

Reproduction Steps

Go to the Provisioner Block docs and follow the link at the end of the section.

Upon arrival at the main provisioners docs, note the absence of a list of provisioners.

Then, follow the link at the end of those docs back to the first doc, noting the claim about what information you will find there.

Upon arrival at the Provisioner Block docs, note the absence of any clear list of "types of provisioner."

Packer version

1.10.x (latest)

Simplified Packer Template

N/A

Operating system and Environment details

N/A (Well, Firefox on Mac OS, but, probably N/A)

Log Fragments and crash.log files

N/A

@anEXPer anEXPer added the bug label Mar 21, 2024
@nywilken nywilken added stage/accepted Confirmed, and intend to work on. No timeline commitment though. docs labels Apr 15, 2024
nywilken pushed a commit that referenced this issue Jun 17, 2024
Updates the provisioners documentation for a better reader experience by including a list of the built-in provisioners and a link to the community supported provisioners that are all withing the navigation tree.

Ref: #12898

Signed-off-by: Ryan Johnson <[email protected]>
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 Jul 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug docs stage/accepted Confirmed, and intend to work on. No timeline commitment though.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants