archive-gh-me/serverless
1
0
Fork 0
mirror of https://github.com/serverless/serverless.git synced 2026-01-25 15:07:39 +00:00
Code Issues Projects Releases Wiki Activity

Use core template for initial stack create

Browse Source
This commit is contained in:
Frank Schmid 2017-03-24 18:26:22 +01:00 committed by Eslam A. Hefnawy
parent 802ce6053d
commit bcd6cee286
2 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
lib/plugins/aws/package/lib/generateCoreTemplate.js
View File

@ -62,7 +62,7 @@ module.exports = {
this.serverless.service.provider.compiledCloudFormationTemplate);
this.serverless.service.provider.coreCloudFormationTemplate =
_.clone(this.serverless.service.provider.compiledCloudFormationTemplate);
_.cloneDeep(this.serverless.service.provider.compiledCloudFormationTemplate);
return BbPromise.resolve();
},

11
lifecycle-changes.md
View File

@ -69,10 +69,11 @@ In general, the addition of event deprecation enables all plugin authors (may it
be the Serverless team or external ones) to get rid of old implementations over
time and encourage people to adapt and use new technologies.
#### Decaring events as deprecated
#### Declaring events as deprecated
To declare an event as deprecated, simply prefix it with `deprecated#` and optionally
add the new event that it will be redirected to with `->` at the end. This allows you even to "redirect" deprecated events to completely different events in
add the new event that it will be redirected to with `->` at the end. This allows you
even to "redirect" deprecated events to completely different events in
different commands.
I know that this looks really ugly in the lifecycle array, but this is intentional.
@ -214,6 +215,8 @@ the `deploy`command.
**package:compileFunctions**
**package:compileEvents**
**package:finalize**
-> aws:package:finalize:mergeCustomProviderResources
@ -256,6 +259,10 @@ aws:common:validate | Performs the global validation (../lib/validate)
* Unit tests for new spawn() call signature
spawn() now accepts specifying commands as string ('cmd:subcmd:subcmd').
We need a unit test for that.
* Deploy
* Unit tests for extended validation
* Check state restore and save
* Check file exist checks
# Sample lifecycle implementation (AWS deploy)