Comments (4)
Thanks for raising your first issue, the team appreciates the time you have taken 😉
from psrule.
Thanks for reporting the issue @Werewolfkiss.
Are you able to provide a sample implementation of ../../../vdl-ets-backoffice/features/Security/Key Vault/v1.2/templates/keyvault.accesspolicies.bicep
that we can use to reproduce the issue?
Doesn't need to be your full internal implementation, just enough of it that fails similarly to the issue you've report. Thanks.
from psrule.
@BernieWhite
Yea no problem its just a module because of scope nothing else so
param keyVaultName string
param accessPolicies array
resource ap 'Microsoft.KeyVault/vaults/accessPolicies@2022-07-01' = {
name: '${keyVaultName}/add'
properties: {
accessPolicies: accessPolicies
}
}
from psrule.
Hi @Werewolfkiss. This should be fixed in PSRule for Azure v1.32.1.
from psrule.
Related Issues (20)
- CLI null reference when include module is undefined
- Investigate Input.IgnoreObjectSource bug
- Tooling shipped with VSCode
- Fail closed support
- CLI discovery of installed modules
- Investigate Rule.Exclude merge improvements
- Fix for git head in tests
- Switch to using PSResourceGet for module installation + add PSGallery as repository if not present. HOT 2
- Using 'Microsoft.Authorization/locks' custom rule, PSRule is returning the wrong 'Reason:' text when failing HOT 4
- PSRule 'Microsoft.Authorization/roleAssignments' is missing type 'properties.principalType' HOT 2
- Ability to exclude rules by tag / pillars HOT 2
- Improve version expression reason
- Fix aggregation of reasons with $Assert.AnyOf()
- `inputPath` set to `some.bicepparam` file works, but throws warning `has not been processed because no matching rules were found` HOT 3
- `Invoke-PSRule -OutputFormat 'Json'` fails if all found rules are in `RULE.EXCLUDE` HOT 1
- Baseline created by data export not found HOT 3
- Expose native logging interface to emitters
- Expose native options interface to emitters
- `Invoke-PSRule -InputPath` treats input as file unless it ends with `[System.IO.Path]::DirectorySeparatorChar`
- Using PSRule v. 3.0.0-B0203 returning unexpected ''helper'' value when testing deployment names using custom rules HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from psrule.