@awsless/awsless 0.0.164 → 0.0.166

package/README.MD

@@ -1,13 +1,13 @@
 
 
 # TODO:
-- onFailure for lambda, sqs, dynamodb streams
-- add cache plugin & think about VPC lambda solutions
 - add fargate container stuff for long lived services
 - add check for existing graphql resolver field in schema
 - add check for conflicting types inside graphql (Like duplicate type names)
   - Types should probably only allowed to defined once. And should be extended after that.
 
+-
+
 ---
 ---
 ---
@@ -35,15 +35,18 @@
 
 We use AWS Route53 to provide domain management.
 
-```js
+```json
 {
-	domains: {
-		'example.com': [{
-			name: 'sub',
-			type: 'A',
-			records: [ ... ],
-		}],
-	}
+  "domains": {
+    "main": {
+      "domain": "example.com",
+      "dns": [{
+        "name": "sub",
+        "type": "A",
+        "records": [ ... ],
+      }]
+    },
+  }
 }
 ```
 
@@ -51,18 +54,11 @@ We use AWS Route53 to provide domain management.
 
 We use AWS Lambda to provide serverless functions.
 
-```js
+```json
 {
-	defaults: {
-		function: {
-			// Setting default values for all functions...
-		}
-	},
-	stacks: [{
-		functions: {
-			FUNCTION_NAME: 'function.ts'
-		}
-	}]
+  "functions": {
+  	"FUNCTION_NAME": "function.ts"
+  }
 }
 ```
 
@@ -70,18 +66,16 @@ We use AWS Lambda to provide serverless functions.
 
 We use AWS DynamoDB to provide serverless tables.
 
-```js
+```json
 {
-	stacks: [{
-		tables: {
-			TABLE_NAME: {
-				hash: 'id',
-				fields: {
-					id: 'string',
-				}
-			}
-		}
-	}]
+  "tables": {
+    "TABLE_NAME": {
+      "hash": "id",
+      "fields": {
+        "id": "number",
+      }
+    }
+  }
 }
 ```
 
@@ -89,11 +83,9 @@ We use AWS DynamoDB to provide serverless tables.
 
 We use AWS S3 to provide serverless key-value storage.
 
-```js
+```json
 {
-	stacks: [{
-		stores: [ 'STORE_NAME' ]
-	}]
+  "stores": [ "STORE_NAME" ]
 }
 ```
 
@@ -107,11 +99,9 @@ _WORK IN PROGRESS..._
 
 We use AWS Open Search Serverless to provide serverless search api.
 
-```js
+```json
 {
-	stacks: [{
-		searchs: [ 'SEARCH_NAME' ]
-	}]
+  "searchs": [ "SEARCH_NAME" ]
 }
 ```
 
@@ -119,13 +109,11 @@ We use AWS Open Search Serverless to provide serverless search api.
 
 We use AWS SQS to provide serverless queues.
 
-```js
+```json
 {
-	stacks: [{
-		queues: {
-			QUEUE_NAME: 'queue-consumer.ts',
-		}
-	}]
+  "queues": {
+    "QUEUE_NAME": "queue-consumer.ts"
+  }
 }
 ```
 
@@ -133,14 +121,12 @@ We use AWS SQS to provide serverless queues.
 
 We use AWS SNS to provide serverless pubsub topics.
 
-```js
+```json
 {
-	stacks: [{
-		topics: [ 'TOPIC_NAME' ],
-		subscribers: {
-			TOPIC_NAME: 'topic-consumer.ts',
-		}
-	}]
+  "topics": [ "TOPIC_NAME" ],
+  "subscribers": {
+    "TOPIC_NAME": "topic-consumer.ts",
+  }
 }
 ```
 
@@ -148,16 +134,14 @@ We use AWS SNS to provide serverless pubsub topics.
 
 We use AWS IoT to provide a serverless mqtt pubsub channel.
 
-```js
+```json
 {
-	stacks: [{
-		pubsub: {
-			PUBSUB_NAME: {
-				sql: `SELECT * FROM '$aws/events/presence/connected/+'`,
-				consumer: 'pubsub-consumer.ts',
-			}
-		}
-	}]
+  "pubsub": {
+    "PUBSUB_NAME": {
+      "sql": "SELECT * FROM '$aws/events/presence/connected/+'",
+      "consumer": "pubsub-consumer.ts",
+    }
+  }
 }
 ```
 
@@ -165,16 +149,14 @@ We use AWS IoT to provide a serverless mqtt pubsub channel.
 
 We use AWS Event Bridge to provide serverless cron jobs.
 
-```js
+```json
 {
-	stacks: [{
-		crons: {
-			CRON_NAME: {
-				schedule: 'rate(1 day)',
-				consumer: 'cron-consumer.ts',
-			}
-		}
-	}]
+  "crons": {
+    "CRON_NAME": {
+      "schedule": "1 day",
+      "consumer": "cron-consumer.ts",
+    }
+  }
 }
 ```
 
@@ -182,16 +164,14 @@ We use AWS Event Bridge to provide serverless cron jobs.
 
 We use AWS ELB to provide a HTTP API.
 
-```js
+```json
 {
-	stacks: [{
-		http: {
-			HTTP_API_NAME: {
-				'GET /posts': 'list-posts.ts',
-				'POST /posts': 'create-post.ts',
-			}
-		}
-	}]
+  http: {
+    HTTP_API_NAME: {
+      'GET /posts': 'list-posts.ts',
+      'POST /posts': 'create-post.ts',
+    }
+  }
 }
 ```
 
@@ -199,16 +179,14 @@ We use AWS ELB to provide a HTTP API.
 
 We use AWS ApiGatewayV2 to provide a serverless REST API.
 
-```js
+```json
 {
-	stacks: [{
-		rest: {
-			REST_API_NAME: {
-				'GET /posts/{id}': 'get-posts.ts',
-				'DELETE /posts/{id}': 'delete-post.ts',
-			}
-		}
-	}]
+  rest: {
+    REST_API_NAME: {
+      'GET /posts/{id}': 'get-posts.ts',
+      'DELETE /posts/{id}': 'delete-post.ts',
+    }
+  }
 }
 ```
 
@@ -216,18 +194,16 @@ We use AWS ApiGatewayV2 to provide a serverless REST API.
 
 We use AWS AppSync to provide a serverless GraphQL API.
 
-```js
+```json
 {
-	stacks: [{
-		graphql: {
-			GRAPHQL_API_NAME: {
-				schema: 'schema.gql',
-				resolvers: {
-					'Query posts': 'list-posts.ts',
-					'Mutation createPost': 'create-post.ts',
-				}
-			}
-		}
-	}]
+  graphql: {
+    GRAPHQL_API_NAME: {
+      schema: 'schema.gql',
+      resolvers: {
+        'Query posts': 'list-posts.ts',
+        'Mutation createPost': 'create-post.ts',
+      }
+    }
+  }
 }
 ```