-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
None
Allow for the service catalog to pass a swagger schema describing the Input Parameters ( Service Characteristics ) for the service. This epic includes adding a new API URI
HTTP GET https://\{api_url}/nbi/api/v1/serviceSpecification/{uuid/specificationInputSchema
to the Service Catalog serviceSpecification to allow the BSS to obtain a copy of the swagger schema file.
Includes updates to the current process of extracting the Tosca Inputs from the sdc catalog service csar, with the persistence of the specificationInputSchema to a DB ( ExtAPI DB )
Will Split this EPIC into the following main stories,
1) Integrate sdc-tosca parser into External API. Using the SDC provided TOSCA parser to parser the Service CSAR from SDC.
2) IntegrateĀ sdc-distribution-client into External API framework to listen for new Services that are distributed.
3) Used Parsed Inputs from Service CSAR to generate and persist swagger Input Schema.
4) Use Parsed Inputs ( including customizationID for resources ) to generate and persist the serviceCatalogResponse
5) Add new API to GET swagger schema from the DB
6) Integrate distribution events receipt to linking to new External API Service to Upload, Parse CSAR and storeĀ swagger file.
- relates to
-
EXTAPI-108 Manage introduct to serviceSpecInputSchema in API serviceCatalog
- Closed