Question: SAM CLI for CI/CD other than Cloud Formation #470
Comments
|
@sthuber90 Github issues is meant for tasks, enhancements/features, and bugs for the project. Support and other questions can be asked in our slack channel (see README.rst), AWS Forums, or Stack Overflow. Closing as this is a general question. |
|
Sorry about that. I opend a question on Stackoverflow. Unfortunatly I wasn't able to tag it with |
mndeveci
added a commit
to mndeveci/aws-sam-cli
that referenced
this issue
May 19, 2023
* Onboarded ruby3.2 * Re-order runtimes in test_cli. * Remove deprecated Python3.6 * Add ruby3.2 to build.yml. * Update build.yml * Update build.yml to run Ruby3.2. * temp: use private lambda builders * temp: use private lambda builders * try * try use GH_TOKEN to access private repo * try use GH_TOKEN to access private repo * try use GH_TOKEN to access private repo * Revert "try use GH_TOKEN to access private repo" This reverts commit eadf4ea650985a4b4fabe5ff82b73eac01dc7c32. * Revert "try use GH_TOKEN to access private repo" This reverts commit a32b86c51ce162ca0680b303dcd889bd65385214. * Revert "try use GH_TOKEN to access private repo" This reverts commit 52ff9084d0c723ce3970ec60ad233343c3fe3157. * Revert "try" This reverts commit 5fc353914e2c126b4a04e2a3b6040356a91787dc. * Revert "temp: use private lambda builders" This reverts commit e39d06f6dc5e0a4ffeee1a2357eafd9b2672d118. --------- Co-authored-by: trivenay <[email protected]> Co-authored-by: Mehmet Nuri Deveci <[email protected]> Co-authored-by: Sean O Brien <[email protected]>
moelasmar
added a commit
that referenced
this issue
May 26, 2023
* Onboarded ruby3.2 * Re-order runtimes in test_cli. * Remove deprecated Python3.6 * Add ruby3.2 to build.yml. * Update build.yml * Update build.yml to run Ruby3.2. * temp: use private lambda builders * temp: use private lambda builders * try * try use GH_TOKEN to access private repo * try use GH_TOKEN to access private repo * try use GH_TOKEN to access private repo * Revert "try use GH_TOKEN to access private repo" This reverts commit eadf4ea650985a4b4fabe5ff82b73eac01dc7c32. * Revert "try use GH_TOKEN to access private repo" This reverts commit a32b86c51ce162ca0680b303dcd889bd65385214. * Revert "try use GH_TOKEN to access private repo" This reverts commit 52ff9084d0c723ce3970ec60ad233343c3fe3157. * Revert "try" This reverts commit 5fc353914e2c126b4a04e2a3b6040356a91787dc. * Revert "temp: use private lambda builders" This reverts commit e39d06f6dc5e0a4ffeee1a2357eafd9b2672d118. --------- Co-authored-by: Mohamed Elasmar <[email protected]> Co-authored-by: trivenay <[email protected]> Co-authored-by: Sean O Brien <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is it possible to use SAM CLI (or any other tool known to mankind) to deploy a lambda function with defined triggers, memory and timeout limits set, etc. the way SAM CLI is able to do it using Cloud Formation?
The text was updated successfully, but these errors were encountered: