Bernie White
Bernie White
PSRule v2 introduced a severity level for rules that can be configured as `Error`, `Warning`, or `Information`. The `Level` can be defined on each rule or inherits from the default...
When a pull request is opened it may be desirable to limit checks to files included in the PR. This would be desirable when externally new rules have been introduced...
Add documentation comments for improving usage of .NET classes and interfaces.
Currently input from files is processed in two ways: - As object by using `-Format Detect` or specific formats such as `Json`, `Yaml`, etc... - This option reads objects from...
## PR Summary - Added repository configuration scan. ## PR Checklist - [x] PR has a meaningful title - [x] Summarized changes - [x] Change is not breaking - [x]...
Currently the CSV output is fixed, providing some additional options to configure the columns include in the output would be useful for some scenarios. Such as adding a description or...
Currently a SHA1 hash is used for name generation as a stable fallback if `TargetName` cannot be bound. While not specifically used in a security context we should look at...
Currently PSRule can be run from PowerShell, Azure Pipelines, and GitHub Actions. Adding support for PSRule via `dotnet tool` would also allow additional integration scenarios. Specifically we'd like to improve...
Currently PowerShell-based rules can use configuration values from options. This is currently not supported for YAML/ JSON rules, we should add this feature. Related to discussion Azure/PSRule.Rules.Azure#1314 May be able...
**Description of the issue** The `$LocalizedData` variable is not exposed to if pre-conditions although should be. **To Reproduce** See Azure/PSRule.Rules.Azure#1401 https://github.com/Azure/PSRule.Rules.Azure/blob/92eeaed44da909ea1118721ea61dde6707e5e5e6/src/PSRule.Rules.Azure/rules/Azure.Common.Rule.ps1#L186-L189 **Module in use and version:** - Module: PSRule -...