Custom modules that replace base modules are not resolved as dependencies properly
seansund opened this issue · 0 comments
seansund commented
Dependencies are resolved via the id
in the module. When custom modules in a custom catalog are intended to replace an existing module, the name
values are the same but the ids are different. This means the BOM resolution will work but dependencies may not be resolved properly.