seems the opposite of what others have been trying to do.. couldn't find much out there.
I am wondering if it's possible to do this without starting a new skill but I can't seem to find any options...
I have a skill that I developed a few years ago as a custom skill in Node.js. It is a custom skill hosted on my own lambda endpoint.
Recently I developed a new copy of the skill which basically does the same thing as the old one, but this time I created it as an Alexa-hosted skill. It is written in Python 3.6 and has some new functionality and upgrades from the old one. It is not live, currently still in development mode.
What I would like to do is point my old, currently-live skill to the new endpoint - which would basically convert it from a self-hosted skill to an Alexa-hosted skill. I went through all the trouble to write this Python code and now I would like to use that code in my old skill (basically replacing the code underneath.)
When I put in my new endpoint value (from the new Alexa-hosted python skill) I get the error like :
The trigger setting for the Lambda arn:aws:lambda:us-east- xxxx is invalid. Error code: SkillManifestError
I found some posts saying you need to edit your triggers on the Lambda function -- the problem is, I can't seem to add a Trigger to the new endpoint because it is Alexa-hosted, so it doesn't show up in my Lambda functions to add triggers.
Is this possible somehow, or am I going to have to rebuild the entire skill? I want to continue with Alexa-hosted rather than setting up a brand new Lambda endpoint on my end, but I was hoping I could just easily swap endpoints on an existing live skill... maybe you can't have 2 alexa-hosted skills pointing to the same endpoint?
Basically - my ultimate goal is that people who currently have my skill installed should be able to continue using the same invocation name and get the new code, without having to re-add the skill. So I'd like to use the existing framework with the existing invocation name that already exists with my old skill, and just change the endpoint.
If I have to I'll set up a new endpoint on Lambda and put my code there but I like the convenience of editing the code directly in the Skills console instead of using the Lambda editor...