Modular Configuration defined in a module can currently be used cross-modules in AO version 7.8. The idea is to restrict the use of Modular Configuration to the module where it is defined i.e. it should not be available cross modules for use.
This is a client requirement for a client in finacial domain. All the passwords are vaulted and they dont want us to use the user/password defined in one module into other module. We need to seek approval before any flows goes live. There is a concern since as of now we can use the modular configuration anywhere in development studio.