Open PetterHL opened 1 week ago
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
Check for previous/existing GitHub issues
Issue Type?
I'm not sure
(Optional) Module Version
0.1.6
(Optional) Correlation Id
No response
Description
Currently, the module avm-res-desktopvirtualization-scalingplan (version 0.1.4) for Azure Virtual Desktop scaling plans hardcodes the virtual_desktop_scaling_plan_schedule using toset. This limits the flexibility to define custom schedules dynamically via variables, which is important for scaling environments where schedules may vary. Is this the intended practice? there is a variable to set "schedules", but this is not used in the main.tf.