You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this was reported as fixed in #450 (comment) for version 0.6.1.
However, with 0.6.2, I'm not seeing a change of the default value reflected in the Cloudformation Parameters in the console, or in the Lambda function.
Steps to reproduce the issue:
with template similar to the one below
package and deploy
Change the Default from red to blue
Check Parameters on the Cloudformation stack, and the Environment on the Lambda function.
Notes:
I've tried this also with --force-upload, but don't see a change that way either.
If I set --parameter-overrides Color=blue, the change is made.
@jrgm The comment you linked is w.r.t sam local commands [invoke|start-api|start-lambda]. The options on package and deploy have not changed and rely on cloudformation's behavior for resolving parameters during stack update/creation.
Description:
I believe this was reported as fixed in #450 (comment) for version
0.6.1
.However, with 0.6.2, I'm not seeing a change of the default value reflected in the Cloudformation Parameters in the console, or in the Lambda function.
Steps to reproduce the issue:
red
toblue
Notes:
--force-upload
, but don't see a change that way either.--parameter-overrides Color=blue
, the change is made.Example template structure:
Output of
sam --version
:Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
Mac OSX
The text was updated successfully, but these errors were encountered: