-
Couldn't load subscription status.
- Fork 77
Add allowed-(guide|resource)-subcategories and allowed-(guide|resource)-subcategories-file arguments to validate
#456
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
Conversation
|
Hi @justinretzolk, Thank you for your contribution. Everything looks good to me, I would just say to update the changelog under |
|
Thanks @rainkwan! I got those changelog entries pushed (neat tool, by the way!) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checks are passing and everything looks good, thank you again for the contribution.
This PR adds options to the
validatecommand to check whether thesubcategorydefined in the YAML frontmatter is within a specified allowlist. This was inspired byYakDriver/tfproviderdocs, which is used by the AWS Provider and AzureRM provider to achieve this functionality.While working on this, I noticed a bug here that led to the incorrect detection of
guidesfiles vs.resource/data-sourcefiles (relErrwasnilwhether files were indocs/resourcesordocs/guides). A fix for that bug is included in this PR.