Skip to content

Commit

Permalink
Added support for markdown output format #114 (#115)
Browse files Browse the repository at this point in the history
  • Loading branch information
BernieWhite authored Feb 4, 2021
1 parent 06ad373 commit 6a65586
Show file tree
Hide file tree
Showing 4 changed files with 11 additions and 9 deletions.
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ What's changed since v0.7.0:
- Added support for using baselines. [#46](https://github.com/microsoft/PSRule-pipelines/issues/46)
- Specify a named baseline by using `baseline: '<baseline_name>'`.
- Baselines can be included from individual files or modules using `source:` and `modules:`.
- Added support for markdown output format. [#114](https://github.com/microsoft/PSRule-pipelines/issues/114)
- Engineering:
- Bump PSRule dependency to v1.0.1. [#106](https://github.com/microsoft/PSRule-pipelines/issues/106)
- See the [change log](https://github.com/microsoft/PSRule/blob/main/docs/CHANGELOG-v1.md#v101)
Expand Down
16 changes: 8 additions & 8 deletions docs/tasks.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,14 +48,14 @@ Syntax:
steps:
- task: ps-rule-assert@0
inputs:
inputType: repository, inputPath # Required. Determines the type of input to use for PSRule.
inputPath: string # Required. The path PSRule will look for files to validate.
modules: string # Optional. A comma separated list of modules to use for analysis.
baseline: string # Optional. The name of a PSRule baseline to use.
source: string # Optional. An path containing rules to use for analysis.
outputFormat: None, Yaml, Json, NUnit3, Csv # Optional. The format to use when writing results to disk.
outputPath: string # Optional. The file path to write results to.
path: string # Optional. The working directory PSRule is run from.
inputType: repository, inputPath # Required. Determines the type of input to use for PSRule.
inputPath: string # Required. The path PSRule will look for files to validate.
modules: string # Optional. A comma separated list of modules to use for analysis.
baseline: string # Optional. The name of a PSRule baseline to use.
source: string # Optional. An path containing rules to use for analysis.
outputFormat: None, Yaml, Json, Markdown, NUnit3, Csv # Optional. The format to use when writing results to disk.
outputPath: string # Optional. The file path to write results to.
path: string # Optional. The working directory PSRule is run from.
```

- **inputType**: Determines the type of input to use for PSRule.
Expand Down
2 changes: 1 addition & 1 deletion tasks/ps-rule-assert/powershell.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ param (

# The output format
[Parameter(Mandatory = $False)]
[ValidateSet('None', 'Yaml', 'Json', 'NUnit3', 'Csv')]
[ValidateSet('None', 'Yaml', 'Json', 'Markdown', 'NUnit3', 'Csv')]
[String]$OutputFormat = (Get-VstsInput -Name 'outputFormat'),

# The path to store formatted output
Expand Down
1 change: 1 addition & 0 deletions tasks/ps-rule-assert/task.json
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,7 @@
"None": "None",
"Yaml": "Yaml",
"Json": "Json",
"Markdown": "Markdown",
"NUnit3": "NUnit3",
"Csv": "Csv"
},
Expand Down

0 comments on commit 6a65586

Please sign in to comment.