Skip to content

Naming conflicts in LogGroupNames using similar function names #7

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Open
timrog opened this issue Dec 16, 2020 · 1 comment
Open

Naming conflicts in LogGroupNames using similar function names #7

timrog opened this issue Dec 16, 2020 · 1 comment

Comments

@timrog
Copy link

timrog commented Dec 16, 2020

The logic to get the LogGroupName is wrong. It searches for a function whose short name ends with the argument, not whose name equals the argument.

That means if you have two functions name lambdafunction and anotherlambdafunction, you can end up with resource conflicts because the LogGroupName for lambdafunction is used for both functions.
timrog added a commit to timrog/serverless-plugin-aws-resource-names that referenced this issue Dec 16, 2020
@timrog
Fix Issue concon121#7
6a372ac
@timrog
Copy link
Author

timrog commented Dec 16, 2020

Actually a dupe of PR #2. Please merge one of them

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@timrog