I've added in the behavior to allow for tagging lambdas during creation and update steps. I used the environment variables as a reference point for how this should behave.
If tags are null, the tags remain untouched on the lambda.
If tags are present, the tags are updated on the lambda to match what is in the deployment. We diff the existing tags and the new tags. Any tags that exist on the lambda but do not exist in the deployment are removed. This is consistent with how the environment variables behave. An empty map will result in all tags being removed from the lambda.
… and migration tasks.
I've added in the behavior to allow for tagging lambdas during creation and update steps. I used the environment variables as a reference point for how this should behave.
If tags are null, the tags remain untouched on the lambda. If tags are present, the tags are updated on the lambda to match what is in the deployment. We diff the existing tags and the new tags. Any tags that exist on the lambda but do not exist in the deployment are removed. This is consistent with how the environment variables behave. An empty map will result in all tags being removed from the lambda.