Hi! After renaming our lambdas in the
ion-config.edn file [], the ion deploy command fails with this cause:
"Function not found:
(Service: AWSLambda; Status Code: 404; Error Code: ResourceNotFoundException; Request ID: <...>; Proxy: null)",
I know that however we rename things in this config file, the deployment steps will delete and then re-create the lambdas under the new names.
If I rollback my config file, the deployment succeeds in recreating the old-named lambdas. But even then, it carries the instruction to delete the inexistent
...-yada-wss-... lambda, as if it thought it's really supposed to be there. What makes it think it's ever been successfully deployed?
If I use my new config file and I comment out the latter half, it succeeds in deploying the
...-yada-app-... lambda, and I see the step machine is asked to delete the inexistent
If I use my new config file without commenting any of its parts, we don't reach the step function because somehow, something expects the
...-yada-wss-... to be already there before calling the step function, which it isn't.
I've been trying for a few hours to find more logs about this. The error happens very quickly before the Step Function state machine could be hit, or the
What's wrong about my
Thanks for any help