Bernie White

Hi @mschwrdtnr most of the detail is already present and is available under the `.Info` or `.Filed` properties. So can be formatted with `Select-Object` and passed to `ConvertTo-Csv`. ```powershell Invoke-PSRule...

Thanks @Mantene for your interest in PSDocs. Sorry we haven't been responsive on this. We have plans to uplift PSDocs to address some challenges for Bicep users, but no immediate...

@Gordonby Thanks for reporting the issue. Sorry for the delay in response. The reason is that the PSRule `requires` option follows SemVer in a similar behaviour as NPM. A version...

> @BernieWhite PSRule has finally been integrated with GitHub workflows. Ref: > > * [[PSRule] Run PSRule pre-flight validation on the whole library (scheduled pipeline) #2425](https://github.com/Azure/ResourceModules/issues/2425) > * [[PSRule] Integrate...

@maythamfahmi Thanks for reporting the error. Are you able to provide a little more detail around `userAssignedScope`? - Is this a variable or parameter in a `.bicep` file? - If...

@maythamfahmi Ok thanks for the additional detail. Some follow up questions. - What is `scope` set from? - Is it the resource `id` of a user-assigned managed identity or something...

Ok great. Thanks for the detail @maythamfahmi. That should allow us to track down the bug.

@maythamfahmi The issue is cause by the resource IDs for the module deployments being incorrectly generated when you have a subscription level target scope and modules targeted to a resource...

@karpikpl Thanks for reporting the issue. Can you confirm you are using a key vault reference in the calling deployment or parameter file?

Ok thanks for that @karpikpl. Let me investigate these bugs and get back to you.