Closed koskoseu closed 6 years ago
I think I nailed it down. Can you try to create a .ask
directory to your project and add a file ./.ask/config
File content :
{
"deploy_settings": {
"default": {
"skill_id": "",
"was_cloned": false,
"merge": {
"skillManifest": {
"apis": {
"custom": {
"endpoint": {
"uri": "your_lambda_function_name"
}
}
}
}
}
}
}
}
(feel free to adjust the name of the lambda function)
This file is in my .gitignore
and should not be.
Let me know if this fixes your issue, I will add the file back to the repo.
It fixed it for me. Thanks!
great - I pushed the changes to our staging repo for review and then I will update this one.
Do you know if the schema for this .ask/config file is documented anywhere? Ia am having a hard time finding it.
I am afraid the .ask/config schema is not documented. https://developer.amazon.com/docs/smapi/ask-cli-command-reference.html#
Hi,
I went through the other (closed) issue on the same topic, and no joy. I have both ask and awscli set up correctly, as far as I can see (see below for output of executing test commands on both), and a skill.json file in the same folder.
Adding --debug provides no additional output.
Test that awscli is set up properly:
Test that ASK is set up properly (output shows a previously deployed, unrelated, skill)
File listing in current folder
Command line and output
Any insight appreciated.