Runtime: Provide a Manifest "controller" for skill scenarios #700
Description
Is your feature request related to a problem? Please describe.
When a developer has made their Bot available as a Skill (i.e. created a manifest in Composer) we encoded the endpoint as a static URI. During development this URI will change, different developers may use different local developer ports, publishing to Azure will require it to be updated to the executing host endpoint, etc.
Developers adding this skill to their bot will experience runtime issues when sending messages if the URI is incorrect which can be hard to diagnose.
Describe the solution you'd like
Introduce a Skill Manifest controller (or similar) which provides a well known location for manifest retrieval on all bots configured as skills - e.g. /api/skill/manifest. This controller will retrieve a manifest file deployed again in a well known place within the bot and at runtime replace the endpoint entry with the actual running location dynamically, then return the updated manifest to the caller.
This was the technique used by Virtual Assistant Solution Accelerator to resolve this issue experienced extensively by developers.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.