Merge pull request #3449 from SDA-SE/feat/provides-consumse-api
Replace implementsApis with providesApis and add consumesApis
This commit is contained in:
@@ -0,0 +1,6 @@
|
||||
---
|
||||
'@backstage/plugin-api-docs': patch
|
||||
'@backstage/plugin-catalog': patch
|
||||
---
|
||||
|
||||
Replace usage of implementsApis with relations
|
||||
@@ -0,0 +1,6 @@
|
||||
---
|
||||
'@backstage/catalog-model': patch
|
||||
'@backstage/plugin-catalog-backend': patch
|
||||
---
|
||||
|
||||
Add `providesApis` and `consumesApis` to the component entity spec.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
'@backstage/catalog-model': patch
|
||||
---
|
||||
|
||||
Marked the field `spec.implementsApis` on `Component` entities for deprecation on Dec 14th, 2020.
|
||||
|
||||
Code that consumes these fields should remove those usages as soon as possible and migrate to using
|
||||
relations instead. Producers should fill the field `spec.providesApis` instead, which has the same
|
||||
semantic.
|
||||
|
||||
After Dec 14th, the fields will be removed from types and classes of the Backstage repository. At
|
||||
the first release after that, they will not be present in released packages either.
|
||||
|
||||
If your catalog-info.yaml files still contain this field after the deletion, they will still be
|
||||
valid and your ingestion will not break, but they won't be visible in the types for consuming code, and the expected relations will not be generated based on them either.```
|
||||
Reference in New Issue
Block a user