We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When calling New-PSRuleOption or Set-PSRuleOption -PassThru an PSRule options object is returned to the pipeline.
New-PSRuleOption
Set-PSRuleOption -PassThru
The output looks like this:
Baseline : PSRule.Configuration.BaselineOption Binding : PSRule.Configuration.BindingOption Execution : PSRule.Configuration.ExecutionOption Input : PSRule.Configuration.InputOption Logging : PSRule.Configuration.LoggingOption Output : PSRule.Configuration.OutputOption Suppression : {} Pipeline : PSRule.Configuration.PipelineHook
To see any configuration options properties need to be expanded or formatted with something like Format-Custom.
Format-Custom
Both of these options are less desirable because they require an additional step and again are not formatted in a format easy to consume.
Since the native format of PSRule options is YAML, which is also generally easy to read, using this format would be ideal.
The text was updated successfully, but these errors were encountered:
Fix YAML options discovery and display #232 #233
c753c6f
Fix YAML options discovery and display #232 #233 (#234)
0d57f6d
BernieWhite
Successfully merging a pull request may close this issue.
When calling
New-PSRuleOption
orSet-PSRuleOption -PassThru
an PSRule options object is returned to the pipeline.The output looks like this:
To see any configuration options properties need to be expanded or formatted with something like
Format-Custom
.Both of these options are less desirable because they require an additional step and again are not formatted in a format easy to consume.
Since the native format of PSRule options is YAML, which is also generally easy to read, using this format would be ideal.
The text was updated successfully, but these errors were encountered: