Remove limitation of blueprint OCI artifacts to one layer

gardener / landscaper

Development of Landscaper - A deployer for K8S workloads with integrated data flow engine.

Apache License 2.0

56 stars 34 forks source link

Remove limitation of blueprint OCI artifacts to one layer #403

Closed Diaphteiros closed 1 year ago

Diaphteiros commented 2 years ago

How to categorize this issue?

/area usability /kind enhancement /priority 5

What would you like to be added: Blueprint OCI artifacts are currently limited to only one layer (see here). This limitation should either be explained in the documentation or, if it is not necessary, removed.

Proposed by @mandelsoft

gardener-robot commented 2 years ago

@Diaphteiros Label area/usabilty does not exist.

achimweigel commented 1 year ago

@In-Ko closed because outdated and/or copied into internal project