Understand the problem
The blueprint of an Installation is currently given by specifying:
- a component version
- and the name of a resource in this component version.
componentDescriptor:
ref:
componentName: github.com/openmcp-project/landscaper-examples/guided-tour
version: 1.0.0
blueprint:
ref:
resourceName: blueprint
It should also be possible to specify:
- a component version
- and a resource in a referenced component version (possibly following a path of several references). One option would be: instead of a
resourceName, also support to specify the blueprint resource in form of a uri cd://componentReferences/<REF_NAME_1>/.../componentReferences/<REF_NAME_N>/resources/<RESOURCE_NAME> (as for example in subinstallations).
componentDescriptor:
ref:
componentName: github.com/gardener/landscaper-examples/guided-tour
version: 1.0.0
blueprint:
ref:
resourceURI: "cd://componentReferences/ref1/resources/blueprint"
Context
Proposal Acceptance Criteria
How much traction does this feature have?
Understand the problem
The blueprint of an Installation is currently given by specifying:
It should also be possible to specify:
resourceName, also support to specify the blueprint resource in form of a uricd://componentReferences/<REF_NAME_1>/.../componentReferences/<REF_NAME_N>/resources/<RESOURCE_NAME>(as for example in subinstallations).Context
Affects the implementation of the Resolve function for blueprints.
Time estimation: < 1 week
Proposal Acceptance Criteria
How much traction does this feature have?