paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 23 Packages Projects Releases Wiki Activity

feat(catalog): processor priority

Browse Source 
This change enables the ordering of catalog processors by their priority,
allowing for more control over the catalog processing sequence.
The default priority is set to 20, and processors can be assigned a custom
priority to influence their execution order. Lower number indicates higher priority.
The priority can be set by implementing the `getPriority` method in the processor class
or by adding a `catalog.processors.<processorName>.priority` configuration
in the `app-config.yaml` file. The configuration takes precedence over the method.

closes #30963

Signed-off-by: Hellgren Heikki <heikki.hellgren@op.fi>
This commit is contained in:
Hellgren Heikki
2025-08-22 10:37:53 +03:00
parent c6558da068
commit 2bbd24f58f
6 changed files with 59 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/software-catalog/life-of-an-entity.md
+4
View File
@@ -132,6 +132,10 @@ in the registration order, but this does not apply over multiple catalog modules
the order of registration depends on the order in which the modules are loaded
by the framework.
It's possible to customize the order of the processors by modifying the
`catalog.processors.<processorName>.priority` configuration option.
The default priority is `20`, and lower value means that the processor runs earlier.
:::
Each step has the opportunity to optionally modify the entity, and to optionally