archive-gh-me/serverless
1
0
Fork 0
mirror of https://github.com/serverless/serverless.git synced 2026-01-18 14:58:43 +00:00
Code Issues Projects Releases Wiki Activity

Remove aws.Resources references in READMEs and tests

Browse Source
This commit is contained in:
Philipp Muens 2016-06-21 12:05:34 +02:00
parent c84f5e93aa
commit 4d8bec0d53
8 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
lib/plugins/aws/deploy/README.md
View File

@ -12,7 +12,7 @@ template (this makes sure that custom resources the user has defined inside the
The parsed resources are attached to the `Service` class. You can access them like this:
```
serverless.service.resources.aws.Resources
serverless.service.resources.Resources
```
**Note:**
@ -24,7 +24,7 @@ previously created CloudFormation template to AWS.
At the end it hooks into [`deploy:deploy`](/lib/plugins/deploy) lifecycle to zip the lambda function and
uploads it to the core S3 bucket (which is defined in the core CloudFormation template). Furthermore it updates the
stack with all the Resources which are defined in `serverless.service.resources.aws.Resources`.
stack with all the Resources which are defined in `serverless.service.resources.Resources`.
The stack status is checked every 5 seconds with the help of the CloudFormation API. It will return a success message if
the stack status is `CREATE_COMPLETE` or `UPDATE_COMPLETE` (depends if you deploy your service for the first time or

2
lib/plugins/aws/deploy/compile/events/apiGateway/README.md
View File

@ -12,7 +12,7 @@ defined, an API Gateway REST API will be created.
Furthermore a lambda permission for the current function is created which makes is possible to invoke the function when
the endpoint is accessed.
Those resources are then merged into the `serverless.service.resources.aws.Resources` section.
Those resources are then merged into the `serverless.service.resources.Resources` section.
## Universal JSON request template

2
lib/plugins/aws/deploy/compile/events/s3/README.md
View File

@ -15,7 +15,7 @@ events.
Furthermore a lambda permission for the current function is created which makes is possible to call the function
when the `s3:objectCreated:*` event is fired.
Those two resources are then merged into the `serverless.service.resources.aws.Resources` section.
Those two resources are then merged into the `serverless.service.resources.Resources` section.
## Event syntax

2
lib/plugins/aws/deploy/compile/events/s3/tests/index.js
View File

@ -16,7 +16,7 @@ describe('awsCompileS3Events', () => {
});
describe('#compileS3Events()', () => {
it('should throw an error if the aws resource is not available', () => {
it('should throw an error if the resource section is not available', () => {
awsCompileS3Events.serverless.service.resources.Resources = false;
expect(() => awsCompileS3Events.compileS3Events()).to.throw(Error);
});

2
lib/plugins/aws/deploy/compile/events/schedule/README.md
View File

@ -13,7 +13,7 @@ is defined within.
Furthermore a lambda permission for the current function is created which makes is possible to invoke the function at
the specified schedule.
Those two resources are then merged into the `serverless.service.resources.aws.Resources` section.
Those two resources are then merged into the `serverless.service.resources.Resources` section.
## Event syntax

2
lib/plugins/aws/deploy/compile/events/schedule/tests/index.js
View File

@ -16,7 +16,7 @@ describe('awsCompileScheduledEvents', () => {
});
describe('#compileScheduledEvents()', () => {
it('should throw an error if the aws resource is not available', () => {
it('should throw an error if the resource section is not available', () => {
awsCompileScheduledEvents.serverless.service.resources.Resources = false;
expect(() => awsCompileScheduledEvents.compileScheduledEvents()).to.throw(Error);
});

2
lib/plugins/aws/deploy/compile/functions/README.md
View File

@ -9,4 +9,4 @@ This plugins compiles the functions in `serverless.yaml` to CloudFormation resou
It loops over all functions which are defined in `serverless.yaml`.
Inside the function loop it creates corresponding lambda function resources which will be merged into the
`serverless.service.resources.aws.Resources` section.
`serverless.service.resources.Resources` section.

2
lib/plugins/aws/deploy/compile/functions/tests/index.js
View File

@ -81,7 +81,7 @@ describe('AwsCompileFunctions', () => {
});
describe('#compileFunctions()', () => {
it('should throw an error if the aws resource is not available', () => {
it('should throw an error if the resource section is not available', () => {
awsCompileFunctions.serverless.service.resources.Resources = false;
expect(() => awsCompileFunctions.compileFunctions()).to.throw(Error);
});