sonyxperiadev/amazon-custom-resources

lambda-with-config should not support FunctionName

Closed this issue · 1 comments

jankronquist commented

Instead use stackName+LogicalResourceId+random like AWS::Lambda::Function.

current problems:

  • FunctionName cannot be changed
  • forces developers to name things that is not needed
jrask commented

I face this when deploying same lambda more than once so its a great idea. Should not be a problem to fix I guess?