serverless / serverless/serverless

How-to/Can-we use serverless for modifying existing cloudformation stack?

Open
#6,694 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cat/deployment question
Dominant language
JavaScript
Stars
46.9k
Forks
5.7k
Avg merge
10h 7m
Merged PRs (30d)
57

Description

Let's say, I have deployed my lambda and API gateway using cloud formation. Now I want to start using the serverless framework, so how do I point my new serverless template to point to existing cloud formation stack to make changes? Is it possible? If yes then how? Can someone please give a small example or reference docs? I know I can drop the existing resources and recreate them but that is not a good option for me.

If this happens successfully then I am going to use to this in my production so let me know of any worst-case failure scenarios also. Will my template delete everything and recreate or it will just override on my existing stack?

Thanks for helping : )

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. First determine whether Serverless Framework can adopt an existing CloudFormation stack, then document a minimal example and the expected update, deletion, recreation, and failure behavior; done when the migration guidance answers those production concerns.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, documentation, infrastructure
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.