Skip to content

Commit 3b3640c

Browse files
authored
Merge branch 'main' into main
2 parents 1125b60 + 80c32f1 commit 3b3640c

File tree

3 files changed

+102
-1
lines changed

3 files changed

+102
-1
lines changed

Diff for: .github/workflows/codeql-analysis.yml

+70
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# For most projects, this workflow file will not need changing; you simply need
2+
# to commit it to your repository.
3+
#
4+
# You may wish to alter this file to override the set of languages analyzed,
5+
# or to provide custom queries or build logic.
6+
#
7+
# ******** NOTE ********
8+
# We have attempted to detect the languages in your repository. Please check
9+
# the `language` matrix defined below to confirm you have the correct set of
10+
# supported CodeQL languages.
11+
#
12+
name: "CodeQL"
13+
14+
on:
15+
push:
16+
branches: [ main ]
17+
pull_request:
18+
# The branches below must be a subset of the branches above
19+
branches: [ main ]
20+
schedule:
21+
- cron: '43 0 * * 5'
22+
23+
jobs:
24+
analyze:
25+
name: Analyze
26+
runs-on: ubuntu-latest
27+
permissions:
28+
actions: read
29+
contents: read
30+
security-events: write
31+
32+
strategy:
33+
fail-fast: false
34+
matrix:
35+
language: [ 'go' ]
36+
# CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python', 'ruby' ]
37+
# Learn more about CodeQL language support at https://git.io/codeql-language-support
38+
39+
steps:
40+
- name: Checkout repository
41+
uses: actions/checkout@v2
42+
43+
# Initializes the CodeQL tools for scanning.
44+
- name: Initialize CodeQL
45+
uses: github/codeql-action/init@v1
46+
with:
47+
languages: ${{ matrix.language }}
48+
# If you wish to specify custom queries, you can do so here or in a config file.
49+
# By default, queries listed here will override any specified in a config file.
50+
# Prefix the list here with "+" to use these queries and those in the config file.
51+
# queries: ./path/to/local/query, your-org/your-repo/queries@main
52+
53+
# Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
54+
# If this step fails, then you should remove it and run the build manually (see below)
55+
- name: Autobuild
56+
uses: github/codeql-action/autobuild@v1
57+
58+
# ℹ️ Command-line programs to run using the OS shell.
59+
# 📚 https://git.io/JvXDl
60+
61+
# ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
62+
# and modify them (or add more) to build your code if your project
63+
# uses a compiled language
64+
65+
#- run: |
66+
# make bootstrap
67+
# make release
68+
69+
- name: Perform CodeQL Analysis
70+
uses: github/codeql-action/analyze@v1

Diff for: events/README_KinesisDataAnalytics.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Sample function
22

3-
The following is an example for an Application Destination Lambda function that receives Amazon Kinesis Data Analytics event records as an input. To send Kinesis Data Analytics output records the Lamdbda function must be compliant with the (required input and return data models)[https://docs.aws.amazon.com/kinesisanalytics/latest/dev/how-it-works-output-lambda.html], so the handler returns a list of delivery statuses for each record.
3+
The following is an example for an Application Destination Lambda function that receives Amazon Kinesis Data Analytics event records as an input. To send Kinesis Data Analytics output records the Lambda function must be compliant with the (required input and return data models)[https://docs.aws.amazon.com/kinesisanalytics/latest/dev/how-it-works-output-lambda.html], so the handler returns a list of delivery statuses for each record.
44

55
The following Lambda function receives Amazon Kinesis Data Analytics event record data as an input and writes some of the record data to CloudWatch Logs. For each entry it adds an element to the response slice, marking it delivered. When the logic considers the delivery to be failed the `events.KinesisAnalyticsOutputDeliveryFailed` value should be used for the response `Result` field.
66

Diff for: events/streams.go

+31
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
package events
2+
3+
// KinesisEventResponse is the outer structure to report batch item failures for KinesisEvent.
4+
type KinesisEventResponse struct {
5+
BatchItemFailures []KinesisBatchItemFailure `json:"batchItemFailures"`
6+
}
7+
8+
// KinesisBatchItemFailure is the individual record which failed processing.
9+
type KinesisBatchItemFailure struct {
10+
ItemIdentifier string `json:"itemIdentifier"`
11+
}
12+
13+
// DynamoDBEventResponse is the outer structure to report batch item failures for DynamoDBEvent.
14+
type DynamoDBEventResponse struct {
15+
BatchItemFailures []DynamoDBBatchItemFailure `json:"batchItemFailures"`
16+
}
17+
18+
// DynamoDBBatchItemFailure is the individual record which failed processing.
19+
type DynamoDBBatchItemFailure struct {
20+
ItemIdentifier string `json:"itemIdentifier"`
21+
}
22+
23+
// SQSEventResponse is the outer structure to report batch item failures for SQSEvent.
24+
type SQSEventResponse struct {
25+
BatchItemFailures []SQSBatchItemFailure `json:"batchItemFailures"`
26+
}
27+
28+
// SQSBatchItemFailure is the individual record which failed processing.
29+
type SQSBatchItemFailure struct {
30+
ItemIdentifier string `json:"itemIdentifier"`
31+
}

0 commit comments

Comments
 (0)