Describe the bug
The security pipeline currently fails as it is missing our default outputs (specifically 'resourceID') as that schema doesn't really fit the module. We need to find a way to deal with this failed test. Following a couple suggestions:
- We can provide the description
@description('The resource ID of the security center. Note: This value is empty.') for an output output resourceId = ''.
- Update the tests by
- Fetching from the Folder-Path what the primary resource is
- Check if there is such a resource in the template
- if not, like in case of the Security Center, no ID would be required
- if so, make sure the *resourceID output exists
To reproduce
Run the current global Pester tests on the SecurityCenter module
Code snippet
No response
Relevant log output
No response
Describe the bug
The security pipeline currently fails as it is missing our default outputs (specifically 'resourceID') as that schema doesn't really fit the module. We need to find a way to deal with this failed test. Following a couple suggestions:
@description('The resource ID of the security center. Note: This value is empty.')for an outputoutput resourceId = ''.To reproduce
Run the current global Pester tests on the SecurityCenter module
Code snippet
No response
Relevant log output
No response