Open dariopellegrini opened 3 years ago
I don't know what the underlying issue is but manually deleting the API-resources under "Amazon API Gateway" seemed to allow me to continue deploying at least.
Did you have any previous deployments? Or maybe Kotless deployments previously failed for some reason?
Yes, I did have a previous deployment. I've been trying to figure out what is causing my existing ktor-application deployment to misbehave so I can't guarantee I haven't been hammering away a little bit too hard ;)
My first attempt at getting back to a working state was to tear down everything (using destroy) and set it back up, which worked but took a long time to get back up and running (mostly because of DNS TTLs I think). The second time the error appeared I did the manual remove.
My method now is to remove everything ktor-related in my existing application and add it back piece-by-piece and so far I haven't seen the error pop up again.
@TanVD I found one situation where the Cycle-error appeared which is when I changed the mergeLambda
-optimization parameter. When I changed it back to the previous value the error disappeared. So:
None
-> All
(Cycle-error)All
-> None
(Error is gone again)As one might expect there was a large difference between what the plan stages (None vs All) were reporting before I attempted the deploys. Hope that helps.
Edit:
Also, it seems to appear when I remove a route from app.routing { }
As mentioned by @djohnsson the problem disappears after deleting lambdas created by Kotless on S3. I have to do that every time I redeploy. Not a solution in my opinion.
I'm experiencing this error when using Kotless with Ktor during Gradle deploy.
My gradle configurations.
Before doing this I deployed correctly using Kotless DSL on that bucket. It seems there is some kind of conflict. Everything is working well using gradle local with Ktor.
Thank you.