Closed ckhicks closed 6 years ago
Can you try again with "skillId"?
I tried replacing skill_id
with either skillid
or skillId
in my app.json
and am getting the same error.
I also see that I'm getting the following for googleAction
deployments as well:
β― Deploying Google Action
β Creating file /googleAction/dialogflow_agent.zip
Language model: en-US
Fulfillment Endpoint: <my lambda endpoint>
β Uploading and restoring agent for project crucible-radio
β Training started
β Uploading to lambda
-> Missing credentials in config
Possibly related?
Could you show me the content of your skill.json
after jovo build
?
Yessir, here it is!
{
"manifest": {
"publishingInformation": {
"locales": {
"en-US": {
"summary": "Sample Short Description",
"examplePhrases": [
"Alexa open hello world"
],
"name": "alexa-crucible-radio",
"description": "Sample Full Description"
}
},
"isAvailableWorldwide": true,
"testingInstructions": "Sample Testing Instructions.",
"category": "EDUCATION_AND_REFERENCE",
"distributionCountries": []
},
"apis": {
"custom": {
"endpoint": {
"sslCertificateType": "Wildcard",
"uri": <my lambda endpoint>
}
}
},
"manifestVersion": "1.0"
}
}
OK. Is your AWS default config linked to the ASK default user? You can see all the ASK users with ask init
It appears to be:
Profile Associated AWS Profile
[default] "__AWS_CREDENTIALS_IN_ENVIRONMENT_VARIABLE__"
Hm, could you maybe try to create a default AWS profile, not the environment variables? It's explained here: https://www.jovo.tech/guides/deploy-lambda-cli#set-up-credentials-with-ask-cli
Ah, it seems that was the issue! I had set one up before but somewhere along the line my .aws/config
file had become malformed with spaces between the variables and their values. Probably something my IDE did when I checked that earlier. Now I just have to sort out my interaction model bugs that didn't show until now. π€¦ββοΈ Thanks for the help!
No problem π
I can confirm these issues with setting up ask-cli to use environment variables. :(
Hi @kaaloo, have you tried setting it up again without the environment variables (https://www.jovo.tech/guides/deploy-lambda-cli#set-up-credentials-with-ask-cli) or is it that you specifically want to use those?
Yes works fine without env vars but I prefer using tools like envchain for sensitive values in the environment.
You're correct @kaaloo . Will consider this for v2
of the CLI (@janober is currently working on it)
Hi, i have same issue when trying to deploy for alexa model
β― Deploying Alexa Skill
β Updating Alexa Skill project for ASK profile default
-> askApiUpdateSkill:Resource not found.
Deploying Interaction Model, waiting for build
Is it an existing skill in your ASK console, @spham?
If yes:
Make sure the skill with the skill id in /platforms/alexaSkill/.ask/config is accessible by the default
ASK profile
If no:
Set skillId
to "" in /platforms/alexaSkill/.ask/config
I'm submitting a...
Expected Behavior
After a successful
jovo build
, I attempt to runjovo deploy -p alexaSkill
and expect to see the lambda endpoint updated. Myapp.json
has the following:Current Behavior
Result of above commands:
Error log
Your Environment