Hi @antonbabenko, I've updated this PR in accordance with your comments, please review when you get a chance.

For the package.{tf,py} I see that it is possible to update the Lambda architecture without changing the filename:

1. Update a function to use different architecture:

   Terraform will perform the following actions:
    # module.lambda_function.aws_lambda_function.this[0] will be updated in-place
    ~ resource "aws_lambda_function" "this" {
    ~ architectures = [
    - "x86_64",
    + "arm64",
    ]
    id = "clear-earwig-lambda-async"
    ~ last_modified = "2021-10-02T13:04:47.276+0000" -> (known after apply)
    tags = {}
    # (18 unchanged attributes hidden)
    # (1 unchanged block hidden)
    }
   Plan: 0 to add, 1 to change, 0 to destroy.
   

2. Apply the changes:

   > terraform apply .plan
   module.lambda_function.aws_lambda_function.this[0]: Modifying... [id=clear-earwig-lambda-async]
   module.lambda_function.aws_lambda_function.this[0]: Modifications complete after 7s [id=clear-earwig-lambda-async]
   Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
   

Can you also update a complete example to show compatible_architectures in Lambda Layer? Then this PR will be good to merge.

Thanks @antonbabenko, compete example has been updated to include compatible_architectures in Lambda layers.

Thank you, @Infra-Red !

v2.20.0 has been just released.

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.