Currently dcaegen2/platform/blueprints repo contains template for services started via DCAE bootstrap.  The template during build get pushed in nexus raw (under release specific folder) from where bootstrap container (under dcaegen2/deployment) sources during build.

This staged approach adds complexity and delays for delivery.

Would propose following changes

1) Move DCAE bootstrap container build  to dcaegen2/platform/blueprint repo (and remove under dcaegen2/deployment)

2) Change bootstrap to load all blueprint directly (instead of sourcing from raw)

3) Change all current blueprint to de-templatized version

4) Move all blueprint under service component repo (on-demand deployed) into blueprint repo.  The blueprint must point to released container version with all default input field populated; deployment result on DCAE environment should be provided for gerrit reviews.

5) Update OOM helm chart for bootstrap to list all release version of service containers (mainly for documentation/release tracking)

Note: There is no change to current list of bootstrapped DCAE MS under this proposal.

For non-static deployed component, an extension will be to push these release version of blueprints into InventoryAPI during deployment to make it available via CLAMP/DeploymentHandler/Dashboard API for dynamic deploy/undeploy. This work will be tracked as separate Jira (DCAEGEN2-2049)