Parameter override in stacks doesn't override the global one

[mpratsch]

Hi Eamonn.

Describe the bug
Our puppet manifest.yaml contains a parameter section what looks like that:

  MasterAccountId:
    default: "xxxxx"
  OrgID:
    default: "o-xxxxx"
  LambdaLayerArn
    default: "arn:aws:lambda:eu-central-1:xxxxx:layer:cfn_custom_resource_layer_v5:2"

In a resource in the stacks section we have something like that:

vpc-tagging:
    name: vpc-tagging
    active: true
    execution: spoke
    deploy_to:
      tags:
        - tag: "type:accounts"
          regions: default_region
    version: v1
    capabilities:
      - "CAPABILITY_NAMED_IAM"
    parameters:
      LambdaRuntime:
        default: "3.11"
      LambdaLayerArn:
        ssm:
          name: "/deployment/lambda/lambda_layer_library_311"
          account_id: "${AWS::PuppetAccountId}"

As you can see I try to override the LambdaLayerArnin the resource section it differs.
I deployed that but the lambda layer remains the one from the global parameter section.

Is that by indention or a bug?

This layer is deployed in our puppet account and exists and works when we defined a different variable name.
The stack itself has no default value defined.

Expected behavior
It overrides the value from the global parameter section to the stacks/launches/.. section.

[eamonnfaherty]

Parameters declared at the stack level should override global. Global has the lowest priority. On 23 Feb 2024, at 07:48, Martina Rath ***@***.***> wrote:  Hi Eamonn. Describe the bug Our puppet manifest.yaml contains a parameter section what looks like that: parameters: MasterAccountId: default: "xxxxx" OrgID: default: "o-xxxxx" LambdaLayerArn default: "arn:aws:lambda:eu-central-1:xxxxx:layer:cfn_custom_resource_layer_v5:2" In a resource in the stacks section we have something like that: vpc-tagging: name: vpc-tagging active: true execution: spoke deploy_to: tags: - tag: "type:accounts" regions: default_region version: v1 capabilities: - "CAPABILITY_NAMED_IAM" parameters: LambdaRuntime: default: "3.11" LambdaLayerArn: ssm: name: "/deployment/lambda/lambda_layer_library_311" account_id: "${AWS::PuppetAccountId}" As you can see I try to override the LambdaLayerArnin the resource since it differs. I deployed that but the lambda layer remains the one from the global parameter section. Is that by indention or a bug? This layer is deployed in our puppet account and exists and works when we defined a different variable name. Expected behavior It overrides the value from the global parameter section to the stacks/launches/.. section. — Reply to this email directly, view it on GitHub<#706>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AACCZFUUDP2J6YWATO5IECLYVCFZDAVCNFSM6AAAAABDWVKKDOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE2TCMBRHEYTGNA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mpratsch]

I would also see it like that but it doesn't worked. I noticed that already multiple times in that setting.
Can it be a special case because it's coming from ssm and not directly. Although I can't tell you if it works without a ssm parameter definition.

Parameters declared at the stack level should override global. Global has the lowest priority. On 23 Feb 2024, at 07:48, Martina Rath @.> wrote:  Hi Eamonn. Describe the bug Our puppet manifest.yaml contains a parameter section what looks like that: parameters: MasterAccountId: default: "xxxxx" OrgID: default: "o-xxxxx" LambdaLayerArn default: "arn:aws:lambda:eu-central-1:xxxxx:layer:cfn_custom_resource_layer_v5:2" In a resource in the stacks section we have something like that: vpc-tagging: name: vpc-tagging active: true execution: spoke deploy_to: tags: - tag: "type:accounts" regions: default_region version: v1 capabilities: - "CAPABILITY_NAMED_IAM" parameters: LambdaRuntime: default: "3.11" LambdaLayerArn: ssm: name: "/deployment/lambda/lambda_layer_library_311" account_id: "${AWS::PuppetAccountId}" As you can see I try to override the LambdaLayerArnin the resource since it differs. I deployed that but the lambda layer remains the one from the global parameter section. Is that by indention or a bug? This layer is deployed in our puppet account and exists and works when we defined a different variable name. Expected behavior It overrides the value from the global parameter section to the stacks/launches/.. section. — Reply to this email directly, view it on GitHub<#706>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AACCZFUUDP2J6YWATO5IECLYVCFZDAVCNFSM6AAAAABDWVKKDOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE2TCMBRHEYTGNA. You are receiving this because you are subscribed to this thread.Message ID: @.>