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
{{ message }}
This repository was archived by the owner on Mar 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 15, 2026. It is now read-only.
Proposed solution: Make the yaml file from which the configuration is read an optional command line parameter. If lambda is called with -c production.yaml it will use that file instead of config.yaml. I'd find this feature useful too.
Alternatively add a --profile parameter like the one supported by the aws CLI utility that controls which AWS credentials to read from ~/.aws/credentials (and, by extension, which AWS account to connect to). Additional profile-specific settings could be configured under a profiles dict in the config file, e.g., profiles.prod.subnet_ids, etc. This would be more consistent with existing aws workflows.
I've added a --profile option in #93 that you can use to switch between different environments, assuming you have configured those in your .aws/{config,credentials} files.
Activity
kilna-magento commentedon Sep 7, 2017
Proposed solution: Make the yaml file from which the configuration is read an optional command line parameter. If lambda is called with -c production.yaml it will use that file instead of config.yaml. I'd find this feature useful too.
jmehnle commentedon Jan 26, 2018
Alternatively add a
--profileparameter like the one supported by theawsCLI utility that controls which AWS credentials to read from~/.aws/credentials(and, by extension, which AWS account to connect to). Additional profile-specific settings could be configured under aprofilesdict in the config file, e.g.,profiles.prod.subnet_ids, etc. This would be more consistent with existingawsworkflows.jmehnle commentedon Feb 2, 2018
I've added a
--profileoption in #93 that you can use to switch between different environments, assuming you have configured those in your.aws/{config,credentials}files.