“At the moment, we're not supporting Sub for deploymentBucket as we're relying on resolved name during the deployment process and Sub will be resolved by CloudFormation.”
“In light of that I believe that we can safely refactor validateListenerArn to support CloudFormation instructions (and all other valid inputs), and change it to return a string id directly (which we would use as albId)”
1
DeploymentBucket parameters not being replaced · Issue #8951 · serverless/serverless
ALB Listener import syntax considered invalid by lambda alb event config code · Issue #7646 · serverless/serverless
AWS Now Supports Max Retry Attempts · Issue #7012 · serverless/serverless
