fix: remove functionName from transform-host lambdas #9491
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
@searchable
and@predictions
directives create a Lambdafunction via
context.api.host.addLambdaFunction()
. This commitupdates
addLambdaFunction()
to not set the optionalfunctionName
in the CFN. This lets CFN generate a unique name.
The mock functionality also needed to be updated because mock
expects all Lambdas to have this optional property. If the CFN
does not contain a
functionName
, fall back to the resource name.Fixes: #9480