Lambda function is not updated when s3Key changed

[blueacidification]

Describe the bug
My team uses gitops to deploy apps in kubernetes, we thought we could do the same for lambdas.

Steps to reproduce
Apply manifest.

function.yaml

apiVersion: lambda.services.k8s.aws/v1alpha1
kind: Function
metadata:
 name: test-lambda-access-2
 annotations:
   services.k8s.aws/region: eu-central-1
spec:
 name: test-lambda-access-2
 code:
   s3Bucket: lambda-function-devops
   s3Key: my-deployment-package-1.zip
 role: arn:aws:iam::535479077865:role/lambda_basic_execution
 runtime: python3.9
 handler: lambda_function.lambda_handler
 description: function created by ACK lambda-controller e2e tests

Change the s3Key.
The function says successfully synced and has the latest changes.
The function does NOT update on AWS.

Expected outcome
The function is updated with the expected s3Key.

Environment

• Kubernetes version 1.28
• Using EKS (yes/no), if so version? 1.28
• AWS service targeted (S3, RDS, etc.) s3

[a-hilaly]

/assign @Vandita2020

[Vandita2020]

Hey @blueacidification,
Thanks for bringing your issue. We are aware of this issue and are working on it. You can keep a track with this PR.

[blueacidification]

Thank you, can't wait for the results!

[Vandita2020]

Hey @blueacidification,
Letting you know that the support for updating S3Key is available now in ACK. Please go and checkout the feature. Thanks!

[Vandita2020]

/close

[ack-prow]

@Vandita2020: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.