All tasks that don't have an execution role are using 'IamRoleLambdaExecution' erroneously and assuming a lambda is being created, so in cases where no lambdas are found and no execution roles are specified to the tasks, we will probably have a CF validation error.
Fix would be creating execution roles for each task on demand, copy the svs provider.iam.roles.. stuff and also allow custom Iam object for each task, similar to what is done on lambda functions.
If possible propagate these changes to lambda events, making sure hybridless is using svs iam compatible object.
All tasks that don't have an execution role are using 'IamRoleLambdaExecution' erroneously and assuming a lambda is being created, so in cases where no lambdas are found and no execution roles are specified to the tasks, we will probably have a CF validation error.
Fix would be creating execution roles for each task on demand, copy the svs
provider.iam.roles..stuff and also allow custom Iam object for each task, similar to what is done on lambda functions.If possible propagate these changes to lambda events, making sure hybridless is using svs iam compatible object.