Skip to content

Commit eb33409

Browse files
committed
Remove AWS Events
1 parent bc809f5 commit eb33409

File tree

15 files changed

+7
-2348
lines changed

15 files changed

+7
-2348
lines changed

README.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -93,9 +93,11 @@ Since most Lambda functions are triggered by events originating in the AWS platf
9393
import TencentSCFRuntime
9494
import TencentSCFEvents
9595

96-
// In this example we are receiving an SQS Message, with no response (Void).
97-
Lambda.run { (context, message: SQS.Message, callback: @escaping (Result<Void, Error>) -> Void) in
98-
...
96+
// In this example we are receiving CMQ Messages from a CMQ Topic, with no response (Void).
97+
Lambda.run { (context, event: CMQ.Topic.Event, callback: @escaping (Result<Void, Error>) -> Void) in
98+
for record in event.records {
99+
...
100+
}
99101
callback(.success(Void()))
100102
}
101103
```
@@ -114,10 +116,10 @@ import NIO
114116

115117
// Our Lambda handler, conforms to EventLoopLambdaHandler
116118
struct Handler: EventLoopLambdaHandler {
117-
typealias In = SNS.Message // Request type
119+
typealias In = COS.Event // Request type
118120
typealias Out = Void // Response type
119121

120-
// In this example we are receiving an SNS Message, with no response (Void).
122+
// In this example we are receiving a COS Event, with no response (Void).
121123
func handle(context: Lambda.Context, event: In) -> EventLoopFuture<Out> {
122124
...
123125
context.eventLoop.makeSucceededFuture(Void())

Sources/TencentSCFEvents/AWS/ALB.swift

Lines changed: 0 additions & 90 deletions
This file was deleted.

Sources/TencentSCFEvents/AWS/Cloudwatch.swift

Lines changed: 0 additions & 142 deletions
This file was deleted.

0 commit comments

Comments
 (0)