Closed klevak closed 9 years ago
Note: When I attempted then to use --force you'll get
Running "deployApiRevision" task [D] Task source: tasks/deployApiRevision.js Fatal error: invalid revision id. provide either argument as deployApiRevision:{revision_id}
Since the API proxy hasn't been created the first time getDeployedApiRevision will return that error. Can you try calling the default task first? grunt --env=dev,test --username=...
I ended up running 'grunt importApiRevision' then 'grunt deployApiRevision:1' got me started fine. The default task tries to get default revision
That's right. That's actually the intended functionality :+1:. Perhaps documenting it in the README.md makes more sense in this case. What would be more intuitive from your point of view?
On your very first deployment you get a getDeployedApiRevisions error.
Running "getDeployedApiRevisions" task [D] Task source: tasks/getDeployedApiRevisions.js [D] 404 [D] {"content-type":"application/json","date":"Tue, 30 Sep 2014 22:48:47 GMT","content-length":"178","connection":"keep-alive"} [D] { "code" : "messaging.config.beans.ApplicationDoesNotExist", "message" : "APIProxy named my-dashboard-app does not exist in organization llbean-nonprod", "contexts" : [ ] } Warning: Task "getDeployedApiRevisions" failed. Use --force to continue.