When layering a collection on top of an EE builder introspects the lower layers too

[anshulbehl]

When you try to build and EE with a partner collection on top of an already built EE that has its own collection, builder tries to introspect all the collections inside all the layers. This essentially means that if there are EE/s that are created without using builder or using manual build requirements and binary dependencies, it can probably fail to find some custom requirements.

Usecase1: I have created an EE that has an installed requirement not present on pypi and that requirements is part of the collection requirements, if a consumer tries to layer their collection on my collection the builder process will fail

Usecase2: I have created an EE that has an installed bindep that is coming from a closed source, when a consumer tries to layer their collection on top of my collection, it will fail if builder is not attached to the closed source at the time of building new layer.

Ideally, Lower layers should not be introspected when builder is trying to build an EE. Specific issue is related to trying to layer partner collection on top of RH supported EE that has the rhv/ovirt collection built in.

Let me know if specific logs are needed or more info is needed as well

[AlanCoding]

We have never seriously looked into the engineering complexities of layering EEs on top of each other. This would be a major item of work that needs real planning.