Repository structure about resourcemodules HOT 3 CLOSED

@ahmadabdalla Agreed. Right now we have example 'Parameters' in a dedicated folder in each service module. In rare cases they point to a specific use case, but it's not generally the case. However, it makes sense as long as we can maintain those files (in case the module has e.g. a breaking change)

from resourcemodules.

@segraef I guess we can resolve this issue for now and open a new one if the current setup does not suit the needs

from resourcemodules.

@segraef Do we want to address the child resource from a specific resourceType? i.e. Microsoft.Network/virtualNetworks/virtualNetworkPeerings?

• do we want to create 'parameters' in a folder to cater for different deployment scenarios? Which naturally evolves into a specific configuration tailored for use cases. And have a name that suits that specific configuration (i.e. secure-blob-storage.parameters.json)

from resourcemodules.