None of the [default.deploy.parameters] properties are read when there is [dev.deploy.parameters]

[mustafizEnosis]

I am assuming that when I have environment specific parameters, the parameters that have same values for all the environments (dev, staging, prod), can be placed under [default.deploy.parameters]. Am I correct?

For example, here are the common parameters across all environments.

[default.deploy.parameters]
capabilities = "CAPABILITY_IAM"
confirm_changeset = true
fail_on_empty_changeset = false
image_repositories = []

Here are the dev and prod environments.

[dev.deploy.parameters]
stack_name = "cfn-lambda-dev-{{ cookiecutter.project_name }}"
s3_bucket = "sample-bucket"
s3_prefix = "lambda/cfn-lambda-dev-{{ cookiecutter.project_name }}"
disable_rollback = true
parameter_overrides = "Env=\"dev\""

[prod.deploy.parameters]
stack_name = "cfn-lambda-prod-{{ cookiecutter.project_name }}"
s3_bucket = "sample-bucket"
s3_prefix = "lambda/cfn-lambda-prod-{{ cookiecutter.project_name }}"
parameter_overrides = "Env=\"prod\""

Utilize the below commands for deployment.

sam deploy \
      --config-env dev \
      --no-execute-changeset

sam deploy \
      --config-env prod \
      --no-confirm-changeset

[reedham-aws]

I believe in this case the default parameters are meant only to be used in the case where an environment is not provided, so I think this is working as intended. I don't think we can easily change this behavior as it would break existing workflows that expect what you're suggesting to NOT happen.

I'm going to close the issue as 'not planned', but feel free to reopen if you have more questions.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

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.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[MustafizSaadi]

I believe in this case the default parameters are meant only to be used in the case where an environment is not provided, so I think this is working as intended. I don't think we can easily change this behavior as it would break existing workflows that expect what you're suggesting to NOT happen.

In that case, we have to duplicate the same parameters across the environments. Right?

[reedham-aws]

Yes, that is correct.