As an Operations person, I would like there to be a method of configuring the SDNC Context Builder to use service specific API calls so that service provider specific implementations can be supported.

General Information

This story concerns itself with setting up a referenceable API mapping table that can be provisioned with the SDNC Context Builder.  As a minimum this table should reload with a system restart.  Once implemented, updates to the API mapping should be able to be made without requiring code updates. It is expected that changes to this mapping would be irregular/infrequent.  The API mapping to be implemented is as per the referenced table (ie for a specific service there may be corresponding specific APIs.  Where no service or mapping is specified, the generic API should be used. 

 Attachments

• API Mapping table

Value

Usability within environments with pre-existing or more complex suite of SDNC APIs that are service specific

 ** 

Success Criteria

• SDNC successfully loads the API mapping
• Code submitted to ONAP; wiki updated
• Demo to working group
• Alignment to ONAP best practices