Bug fix - Not able to change the max number of VMs in AKS node pool

Bug Details

Currently the AKS module supports for changing the maximum number of node pool VM count. But that is not reflected in usage at service resources AKS creation.

Design Question

Do we need to create the same set of variables required for the module at places where we use, or is there going to be a way to bring forward the variables needed for modules? Or the only way is create same set of variables needed for the modules at the point where we are using and pass them?

PS: This is soon going to be an issue as perf environment is maxing out already on VM count.