-
Notifications
You must be signed in to change notification settings - Fork 41
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
feat: adds terraform-docs as a linter 📄 #946
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
version: 0.1 | ||
lint: | ||
definitions: | ||
- name: terraform-docs | ||
files: [terraform] | ||
main_tool: terraform-docs | ||
description: Generate terraform + tofu module documentation | ||
commands: | ||
- name: terraform-docs | ||
Gowiem marked this conversation as resolved.
Show resolved
Hide resolved
|
||
output: rewrite | ||
formatter: true | ||
run_from: ${target_directory} | ||
run: terraform-docs markdown --output-file=README.md . | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. One note here: This is my team and I's (and I would suspect many many others) most common usage when using Do ya'll have any other configurable plugins that I should check out for inspiration to make sure this doesn't need an immediate update from the 2nd person to use it? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @EliSchleifer any thoughts here or ship it and we can deal with any requests for configurability in the future? |
||
read_output_from: stdout | ||
stdin: true | ||
success_codes: [0] | ||
suggest_if: never | ||
known_good_version: 0.16.0 | ||
version_command: | ||
parse_regex: ${semver} | ||
run: terraform-docs --version |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
import { linterFmtTest } from "tests"; | ||
|
||
linterFmtTest({ linterName: "terraform-docs" }); |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
# This is a test of the emergency broadcast system | ||
|
||
<!-- BEGIN_TF_DOCS --> | ||
<!-- END_TF_DOCS --> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
// Jest Snapshot v1, https://goo.gl/fbAQLP | ||
|
||
exports[`Testing formatter terraform-docs test variables 1`] = ` | ||
"README.md updated successfully | ||
" | ||
`; |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
variable "testing" { | ||
type = string | ||
default = "Hello world" | ||
description = "This is a test of the emergency broadcast system" | ||
} |
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.
The command name should more map what the command does than the name of the tool. So in this case given the formatter nature I would set name to "format"