[X] I have checked for previous/existing GitHub issues
Description
Diverse modules currently fail in main (e.g., due to WAF-reliablity) and can hence not be updated with to lastest RBAC schema as they'd just fail in main again without publishing the update.
This issue is intended to track these modules to enable a future update as they are fixed.
cc: @krbar
### Tasks
- [x] update RBAC schema in `avm/res/api-management/service` (#2980)
- [x] update RBAC schema in `avm/res/container-registry/registry` (#2983)
- [x] update RBAC schema in `avm/res/db-for-postgre-sql/flexible-server` (#3080)
- [ ] update RBAC schema in `avm/res/desktop-virtualization/host-pool` (#3170)
- [ ] update RBAC schema in `avm/res/digital-twins/digital-twins-instance`
- [x] update RBAC schema in `avm/res/document-db/database-account` (https://github.com/Azure/bicep-registry-modules/pull/2907)
- [x] update RBAC schema in `avm/res/network/application-gateway` (https://github.com/Azure/bicep-registry-modules/pull/3121)
- [ ] update RBAC schema in `avm/res/sql/managed-instance`
- [ ] update RBAC schema in `avm/res/power-bi-dedicated/capacity`
- [x] update RBAC schema in `avm/res/sql/instance-pool` (no RBAC in the module, added here by a mistake)
- [ ] update RBAC schema in `avm/res/web/hosting-environment`
- [ ] update RBAC schema in `avm/res/web/serverfarm`
Check for previous/existing GitHub issues
Description
Diverse modules currently fail in main (e.g., due to WAF-reliablity) and can hence not be updated with to lastest RBAC schema as they'd just fail in main again without publishing the update.
This issue is intended to track these modules to enable a future update as they are fixed.
cc: @krbar