-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WAF - Reliability Review] - avm/res/api-management/service
#1473
Comments
Important The "Needs: Triage 🔍" label must be removed once the triage process is complete! Tip For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation. Note This label was added as per ITA06. |
Note The "Type: Feature Request ➕" label was added as per ITA20. |
avm/res/api-management/service
@azure/avm-res-apimanagement-service-module-owners-bicep |
@tony-box, can you please take a look at this one? Thanks! |
I am working to rebuild my test environment due to some issues with it. Will look into this as soon as I can. |
This is fixed in my latest MR #1989 @jtracey93 are you suggesting this change would require a new min version bump? |
Check for previous/existing GitHub issues
Issue Type?
Feature Request
Module Name
avm/res/api-management/service
(Optional) Module Name if not listed above
No response
(Optional) Module Version
No response
Description
Hello team,
The AVM core team are performing a review of all AVM modules to ensure they are aligned to the WAF reliability pillar by default, and in the future they will be checking against other WAF pillars also. This is a requirement we have before we can go
v1.0.0
for any AVM module.Links to AVM specs:
Links to WAF Reliability, APRL & Product Docs recommendations used for analysis:
Whilst reviewing this module the following issues have been found that are non-compliant with the AVM specs that need to be resolved in a new version release:
skuCount
parameter to3
(to match the zones) and adjust/remove the allowed decorator for the modulezones
parameter to[1,2,3]
sku
parameter toPremium
tier to support AZsPlease make these changes in a PR to the parameter defaults so a new minor version can be published.
PSRule
It also seems that PSRule is not picking up these checks under its
Azure.Pillar.Reliability
baseline via its tests and that has been logged in the issue: Azure/PSRule.Rules.Azure#2787And there is also a missing check for the capacity instances which has been logged here: Azure/PSRule.Rules.Azure#2788
Thanks
The AVM Core Team
(Optional) Correlation Id
No response
The text was updated successfully, but these errors were encountered: