CIS 1.3.6 - Pls. Add license check to avoid false positives
The test "CIS 1.3.6 (L2) Ensure the customer lockbox feature is enabled" reports as failed, although we are not able to enable it due to missing licenses. It would be great to have a license check like with the others as well.
@maester365/core-module What do we think of tagging all tests that need a license, with that license LicenseP2. So Maester users can start calling it with -ExcludeTags LicenseP2
@svrooij I think we should do both. The automatic exclusion we already have implemented for many checks should be the default. Tagging them in addition would be a nice way to identify them more easily
I've created a new maester-config.json right now it only has Severity and I was planning on adding other attributes like license etc to it.
I've created a new maester-config.json right now it only has Severity and I was planning on adding other attributes like license etc to it.
Would there be any overlap in tags or other attributes between the test scripts and the JSON config file, or would you move some info fully to the JSON?
We have a number of tests that check license levels, so this should be easy to update.