Serverless upgarde, safety and style #105
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…upon, but are a decent second and third layer. Protect your branches in github. From bigmac
…ccidnetally moved outside provider and into custom, causing errors
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Safety checks were added to destroy.yml and destroy.sh to prevent the deletion of important branches
The version of serverless was upgraded to ^2.7.0. I'm really unclear why it was at 1.82.0, because I could have sworn it was upgraded to 2.x awhile ago.
Styling changes were made, and services were standardized.
This will undoubtedly cause conflicts on existing branches that have diverged, but there's only 1 (local dev) and I'm going to be hands on or working with who's hands on, and the conflicts are simple.