Globals change not caused resources to be re-deployed.

[andyloughran]

Description

After making a modification to the Globals: Function: section of a SAM template, I'd expected the change to proliferate to all of the Serverless::Function's within the template.

Steps to reproduce

I modified: Globals: Functions: Layers to point at a new layer arn.

Observed result

The stack deployed, but the layerARN is still pointing at the legacy one.

Expected result

All functions to have redeployed with the new layer arn.

Additional environment details

1. OS: Linux
2. If using the SAM CLI, sam --version: SAM CLI, version 1.142.1
3. AWS region: eu-west-2

[vicheey]

Thank you. I'll take a look.

[andyloughran]

Thank you. I'll take a look.

I've worked on it further over the weekend and it doesn't appear to be a sam issue, but tied to cfn and {{resolve:}} behaviours with !Sub and env vars in Globals.

I'll come back to you once I've done a more thorough write up.

[vicheey]

Thank you for the update. Let keep us posted. If you can also provide an example template that we can use to reproduce the issue as well, that would be great.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.