I am working on a project that has the requirement to deploy a N-tier solution. For each tier the user is prompted on if the tier is to be included or excluded, and if it is included whether or not network load balancing is included. Meaning that the per-tier options are: (1) none, (2) one sided, (3) two sided with NLB. Right now the solution has one blueprint per tier and an Orchestrator workflow will make a request to vRA to request the appropriate catalog item. The problem with this approach is that there are 'N' number of vRA requests which are not associated with each other. In the case of a four tier configuration with three options per tier (none, Side A, NLB + Side B) there would be a total of 3*3*3*3 = 81 combinations.
Rather than building one blueprint per tier I'm trying to figure out if it is possible to build one uber blueprint will all of the options included and then based on the user's input remove the components that are not required, either by removing entire tiers from the request or by removing NLB+SideB components for a specified tier from the request. At this point the NLB solution is unknown and I would prefer to treat it as a generic black box for now.
Or, would it be easier to build a skeleton blueprint and add the components, either entire tiers or NLB+SideB for specified tiers, to the request?