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 have a project that has both persistent parameters and per-deploy parameters (e.g., one of the lambda functions has to have the current commit hash as an environment variable for error reporting reasons). However, I've noticed that when I use the --parameter-overrides command line argument, it completely ignores the parameter_overrides section of my samconfig.yaml file. I would have expected sam deploy to merge parameter values in “immediacy” order, such as:
Command line --parameter-overrides have highest precedence
samconfig.{toml,yaml}parameter_overrides have next highest precedence
Default values have lowest precedence
Is there a way I can achieve what I'm trying to do without either adding ephemeral values to my config file or putting all overrides on the command line?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a project that has both persistent parameters and per-deploy parameters (e.g., one of the lambda functions has to have the current commit hash as an environment variable for error reporting reasons). However, I've noticed that when I use the
--parameter-overrides
command line argument, it completely ignores theparameter_overrides
section of mysamconfig.yaml
file. I would have expectedsam deploy
to merge parameter values in “immediacy” order, such as:--parameter-overrides
have highest precedencesamconfig.{toml,yaml}
parameter_overrides
have next highest precedenceIs there a way I can achieve what I'm trying to do without either adding ephemeral values to my config file or putting all overrides on the command line?
Beta Was this translation helpful? Give feedback.
All reactions