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

beps/0009: add conflict resolution

Browse Source 
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
Patrik Oldsberg
2024-06-05 15:48:02 +02:00
parent 30aea8403e
commit 830780d6cf
1 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
beps/0009-plugin-metadata/README.md
+10 -1
View File
@@ -135,7 +135,16 @@ The `backstage.pluginPackage` field is required when publishing a package with a
## Design Details
_-_
### Package Relationships Conflict Resolution
Conflicts in the defined metadata are handled as follows:
- The union of all `pluginPackages` is always used. If there are multiple packages defined for the same role, conflicts are resolved using the `backstage.moved` field if possible, but otherwise all packages are rejected.
- All plugin packages with references to each other must have the same `pluginId`, or they are all rejected.
- A module must have the same `pluginId` as the plugin it is a module for, or it is rejected.
- If the role of a package does not match the definition in the `pluginPackages` field, the package is rejected.
When metadata is "rejected" the consumer should either throw an error, or treat the conflicted fields as if they do not exist.
### References & Prior Art