Currently every module brings, if necessary, it own modules with it, if they are needed. For example VM, Azure Firewall and some others can create their own Public IP address. But we also have a stand alone PIP module. The question is, should we only use the stand-alone module and add dependencies between the modules, or should we keep them atomic with the drawback, that one change to PIP for example, needs to be done on all modules that create a PIP. Currently the PIP code is always a bit different, which already shows, we have an issue here.
The PoC should investigate how a local reference (inside the repo) can work.
Currently every module brings, if necessary, it own modules with it, if they are needed. For example VM, Azure Firewall and some others can create their own Public IP address. But we also have a stand alone PIP module. The question is, should we only use the stand-alone module and add dependencies between the modules, or should we keep them atomic with the drawback, that one change to PIP for example, needs to be done on all modules that create a PIP. Currently the PIP code is always a bit different, which already shows, we have an issue here.
The PoC should investigate how a local reference (inside the repo) can work.