Skip to content

Feature: Landscaper: Blueprint Resource in Referenced Component Version #393

@robertgraeff

Description

@robertgraeff

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

  • Code has been reviewed by other team members
  • Internal technical Documentation created/updated
  • New / changed code is documented
  • Unit Tests created for new code or existing Unit Tests updated
  • Enduser Documentation updated
  • Successful demonstration in Review

How much traction does this feature have?

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/feature-request💡 Feature request from any stakeholderneeds/validationVerify Issue and Prio with POsig/extensibilityAll topics related to special interests group openMCP extensibility

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions