It doesn't support custom versions and aliases yet. Curious what your use case is.
It sort of does custom aliases by giving the function an alias with the environment name, but that probably isn't what you want.
It sort of does custom aliases by giving the function an alias with the environment name, but that probably isn't what you want.
What I need to make sure of is that all the lambda functions / roles are updated before the starter so that the workflow doesn't break, as there could be breaking changes between commits.
A suggestion would be to create a repo per lambda function, but that becomes a hassle to manage after a few dozen, and just throws in even more work on ensuring the order of updates necessary. It is easier to flow between commit versions.