refactor: Fix README generation for internal submodules #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We introduced
test_infrastructuremodule as internal submodule from TF Registry perspective. This means that module's README file should have a leading dot in its name (.README.md). We needed to automate the generation of README files for internal submodules.This PR introduces separate terraform-docs configuration file for internal submodules and additional terraform-docs hook in pre-commit configuration file for
test_infrastructuremodule.Motivation and Context
#30
How Has This Been Tested?
Tested locally with
pre-commitcommand.Screenshots (if appropriate)
The terraform-docs hook is ran twice now, like that:
Types of changes
Checklist