As far as I can tell from the docs, there's no way to specify the alias name in the serverless definition itself (please correct me if I'm wrong). This seems weird to me, as it makes sense to have everything custom to the lambdas defined there. The build system that I'm working with also follows this assumption, as it abstracts the actual deployment step away from the lambda definitions themselves.
I haven't tested it yet, but I'm also assuming that the current implementation doesn't give fine-grained support for different aliases on multiple functions. If I have two functions defined in one serverless.yaml file, there's a use case where I want different aliases on each of them.
As far as I can tell from the docs, there's no way to specify the alias name in the serverless definition itself (please correct me if I'm wrong). This seems weird to me, as it makes sense to have everything custom to the lambdas defined there. The build system that I'm working with also follows this assumption, as it abstracts the actual deployment step away from the lambda definitions themselves.
I haven't tested it yet, but I'm also assuming that the current implementation doesn't give fine-grained support for different aliases on multiple functions. If I have two functions defined in one serverless.yaml file, there's a use case where I want different aliases on each of them.