[deployer-aws-lambda]: removes all other associated lambdas from CloudFront

[thejuan]

When deploying to CF, the deployer removes all associated lambdas i.e. a viewer request lambda.
In principal everything should be in the FAB, but for migrations to FAB this is problematic.

[geelen]

Ah yeah I can see how that might be a problem...

Given you're the first person to hit this, do you have a solution in-mind? The deployer needs some way of figuring out which Lambda to replace on each deploy, right? We could bail if we detect >1 lambdas already, but I'm more thinking of this case: this is the first time you've deployed a FAB and there's exactly 1 lambda there already—how do you know whether to replace that one or attach another?

I may be misunderstanding though, it's been a while since I've touched the AWS deployer stuff...

[thejuan]

It looks like you pull down the config from the distribution before updating, so you can just upsert the originRequest handler in the current config.

[thejuan]

It's a nice to have, now I know it replaces i'll just move to the FAB.