Feature Proposal: `sls deploy` should only deploy functions that changed

This is a Feature Proposal

Description

I don’t want to have the responsibility on the user to determine what to deploy, or track what functions changed. The Framework should ‘detect’ what changed, and as a user, I should always be calling sls deploy.

For bug reports:

• What went wrong?
• What did you expect should have happened?
• What was the config you used?
• What stacktrace or error message from your provider did you see?

For feature proposals:

• What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us. - It makes the CLI UI cleaner and simple. It also takes away the responsibility of tracking what changed from the user to the framework.
• If there is additional config how would it look - N/A

Additional Data

• Serverless Framework Version you’re using:
• Operating System:
• Stack Trace:
• Provider Error messages:

[pmuens]

Closing this issue since it’s quite old and serverless deploy will always leverage CloudFormation ehind the scenes. We need to go through a full deployment to ensure a consistent state afterwards.

One can use serverless deploy function to deploy a single function.

[pmuens]

Alright, sorry for lagging on this a bit. Wanted to make sure I took the time to thoroughly think this through.

Thanks for getting back @brettneese 👍 and no worries! IMHO planning things thoroughly is super important (and oftentimes the more important part).

I hope it’s okay that I took the liberty to create a new issue with my proposals: #4071

Just saw that this morning! This is super nice 🎉 💯 super detailed and exactly what we need to have a productive discussion!

Thanks for taking the time to create that 🥇