Skip to content

Resolving componentReferences within values.yaml.tpl #32

Description

@fla-dachs

What would you like to be added:
I would like component references of a component version to be fully resolved and accessible within my values.yaml.tpl

Why is this needed:
I'm using component references for more effective packaging of my application dependencies, and only keep a single container image and helm chart in my parent component version as it changes more frequently during development.

Within said helm chart and its values.yaml.tpl, I would still like to access metadata from the leaf components referenced in componentReferences, like OCIResources, as currently, I would have to define these dependencies within the parent component-constructor and continuously transfer them with every test run.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions