Filtering bundles

ECR bundles are filterable by component from App Builder user interface.

Behind the scenes, filtering is done using the label-based filtering provided out of the box from Kubernetes.

To enable filtering of a bundle, the custom-resource representing the bundle on the Entando Cluster needs to contain the correct labels. An important note on the values to add the the labels field, even if to correctly define a label in a k8s resource both the key and the value are required, from an Entando point of view only the key part of the label is used for filtering. The value could be set to anything, but our reccomendation is to use "true" for clarity and simplicity.

Supported labels keys are:

Label entry	Description
widget: "true"	The bundle contains one or more microfrontends (widgets)
plugin: "true"	The bundle contains one or more microservices (plugins)
fragment: "true"	The bundle contains one or more fragments
page: "true"	The bundle contains one or more pages
pageTemplate: "true"	The bundle contains one or more page templates
contentType: "true"	The bundle contains one or more content types
contentTemplate: "true"	The bundle contains one or more content templates

Example

Here an example of the metadata for a ecr bundle containg micro-frontends, some microservices, pages and page templates

apiVersion: entando.org/v1
kind: EntandoDeBundle
metadata:
  name: demo-bundle
  labels:
    widget: "true"
    plugin: "true"
    page: "true"
    pageTemplate: "true"
spec:
  details:
  ...