- New endpoints included in new release 18 with new logic.
- New logic to support ***Vendor Extensibility*** on Publish Service.
- New logic to support ***Vendor Extensibility*** on Publish and Discover Service.
- New logic to support ***API Status*** feature on Publish and Events Services.
- Supported Features now are mandatory for all POST and PUT Requests as is described on TS 29.222.
-**Possible Breaking change**, all POST request now must include supported features attribute, default can me set to "0" to keep all features inactive.
...
...
@@ -13,11 +13,61 @@
### **Technical Debt Solved**
#### **Vendor Extensibility feature**
- Publish API:
- On publishing a service API, **SupportedFeatures** is read and checked whether VendExt feature is enabled.
- When VendExt is enabled, vendor-specific fields are searched and stored in the db inside the ServiceAPIDescription object
- Vendor-specific fields are added according to the specific format:
- Event internal notifications between services improved to accomplish specification.
- On event subscription **SupportedFeatures** is readed and stored in db to accomplish specification.
- On event subscription **SupportedFeatures** is read and stored in db to accomplish specification.
- Also **SupportedFeatures** is checked before send event notification, in order to accomplish specification, sending **eventDetails** and related information according to ***enhanced_event_report*** and ***apiStatusMonitoring*** supported features activated.