Skip to content

Exception Parameter Backward Compatibility Feature Request #506

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

Closed
bcwilhite opened this issue Sep 18, 2019 · 0 comments · Fixed by #515
Closed

Exception Parameter Backward Compatibility Feature Request #506

bcwilhite opened this issue Sep 18, 2019 · 0 comments · Fixed by #515
Assignees

Comments

@bcwilhite
Copy link
Contributor

Is your feature request related to a problem? Please describe.

4.0 Introduced a new way to enter exceptions. There's a request to allow backward compatibility with the 2.x/3.x way of entering exceptions.

Describe the solution you'd like

Allow both methods for entering exceptions:
4.x: (Which will allow for modification of multiple properties per ruleId)

configuration Example
{
    Import-DscResource -ModuleName PowerSTIG

    Node localhost
    {
        WindowsServer BaseLine
        {
            OsVersion  = '2012R2'
            OsRole     = 'MS'
            DomainName = 'contoso.local'
            ForestName = 'contoso.local'
            Exception  = @{
                'V-1075' = @{
                    ValueData = 1
                }
            }
        }
    }
}

2.x/3.x: (Which will only allow modification of a predetermined property value)

configuration Example
{
    Import-DscResource -ModuleName PowerSTIG

    Node localhost
    {
        WindowsServer BaseLine
        {
            OsVersion  = '2012R2'
            OsRole     = 'MS'
            DomainName = 'contoso.local'
            ForestName = 'contoso.local'
            Exception  = @{
                'V-1075' = 1
            }
        }
    }
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant