lambda: addAlias method fails when there are more than one lambda functions in a stack

[ericxinzhang]

Describe the feature

At the moment the lambda function addAlias method link composes the logic name as Alias${aliasName} which causes error when there are multiple lambda functions in a stack with same alias.

Use Case

I would like to use the SnapStart feature therefore needs to add an alias to all my lambda functions. However I can't use addAlias method because of the duplicate logical name.

Proposed Solution

I'd suggest that the alias name is derived from not only the alias name itself, but also the lambda version so as to make it more unique.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.79.1

Environment details (OS name and version, etc.)

MacOS

[peterwoodworth]

The scope of these should be different, no? Could you provide reproduction code please?

[ericxinzhang]

My apology - it's a false alarm.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.