Skip to content
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

Improve output display of PSRule options #233

Closed
BernieWhite opened this issue Jul 3, 2019 · 0 comments · Fixed by #234
Closed

Improve output display of PSRule options #233

BernieWhite opened this issue Jul 3, 2019 · 0 comments · Fixed by #234
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@BernieWhite
Copy link
Member

BernieWhite commented Jul 3, 2019

When calling New-PSRuleOption or Set-PSRuleOption -PassThru an PSRule options object is returned to the pipeline.

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.

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.

@BernieWhite BernieWhite added the enhancement New feature or request label Jul 3, 2019
@BernieWhite BernieWhite added this to the v0.8.0 milestone Jul 3, 2019
@BernieWhite BernieWhite self-assigned this Jul 3, 2019
@BernieWhite BernieWhite mentioned this issue Aug 3, 2019
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant