amplify-cli: amplify env checkout causes local changes to lambda layer

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

No response

Amplify CLI Version

6.0.0

What operating system are you using?

Mac

Amplify Categories

function

Amplify Commands

env

Describe the bug

Whenever I switch between environments using amplify env checkout X that have a lambda layer, there are changes made to the awscloudformation-template.json and parameters.json for the layer.

Expected behavior

amplify env checkout X should not result in any changes to files that are git committed.

Reproduction steps

I’m not clear yet whether this is expected or not - happy to try to reproduce further if useful.

I have one lambda function, with one lambda layer.

backend-config.json:

 "function": {
    "LambdaWithLayer8ba9f268": {
      "service": "Lambda",
      "providerPlugin": "awscloudformation",
      "build": true,
      "dependsOn": [
        {
          "category": "function",
          "resourceName": "LambdaLayer",
          "attributes": [
            "Arn"
          ]
        }
      ]
    },
    "LambdaLayer": {
      "providerPlugin": "awscloudformation",
      "service": "LambdaLayer",
      "build": true
    }
  },

function parameters.json:

{
  "lambdaLayers": [
    {
      "type": "ProjectLayer",
      "resourceName": "LambdaLayer",
      "env": "dev",
      "version": "Always choose latest version",
      "isLatestVersionSelected": true
    }
  ]
}

Log output

# Put your logs below this line