I have started using a runner image with SAM with spacelift. The cloudformation configuration allows entry_template_file, region, template_bucket, and stack_name.
I then setup Environment variables for CF_PARAM_Environment, and others that get used in my sam template. Previously I was setting the parameters in a config file with the parameter_overrides key.
I have a config file per env and use the [<env>] config grouping, so to use the custom toml file and the right env, I would need to be able to pass —config-file and —config-env to the sam command that spacelift uses.
I prefer to use the config-file so I can manage the values in git within the repo I am deploying, rather than managing them separately in spacelift via environment variables. I may allow developers to modify the config file in their repo, when they don’t have permissions to manage the spacelift stack.
Please authenticate to join the conversation.
⬆️ Gathering votes
💡 Feature Requests
CloudFormation
Over 1 year ago
Get notified by email when there are changes.
⬆️ Gathering votes
💡 Feature Requests
CloudFormation
Over 1 year ago
Get notified by email when there are changes.