@pipeline-builder/pipeline-events 0.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +202 -0
- package/README.md +126 -0
- package/lib/index.d.ts +2 -0
- package/lib/index.js +834 -0
- package/package.json +159 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,126 @@
|
|
|
1
|
+
# @pipeline-builder/pipeline-events
|
|
2
|
+
|
|
3
|
+
📖 **[View documentation](https://mwashburn160.github.io/pipeline-builder/)**
|
|
4
|
+
|
|
5
|
+
AWS Lambda handler for [Pipeline Builder](https://mwashburn160.github.io/pipeline-builder/) that ingests CodePipeline state-change events from EventBridge and forwards normalized payloads to the reporting service.
|
|
6
|
+
|
|
7
|
+
> Internal workspace package. This is not imported by other packages — it is deployed as a Lambda by the CLI's `setup-events` command, which provisions the full EventBridge → SQS → Lambda stack (rule, queue, dead-letter queue, IAM, and this handler).
|
|
8
|
+
|
|
9
|
+
## Responsibilities
|
|
10
|
+
|
|
11
|
+
1. Receives CodePipeline (pipeline / stage / action) events delivered as an SQS batch sourced from EventBridge.
|
|
12
|
+
2. Classifies each record into a normalized event type (`PIPELINE`, `STAGE`, `ACTION`) and derives status, start/completion times, run duration, and — on failures — the `errorMessage` (from the action's `execution-result.external-execution-summary`).
|
|
13
|
+
3. Resolves each pipeline's tags via `codepipeline:ListTagsForResource`, cached per pipeline. The ARN and AWS account never leave AWS, so there is no masking/secret to manage. Untagged (unregistered) pipelines are skipped.
|
|
14
|
+
4. Resolves the DORA **commit range** in-account for source/deploy events (Phase 4) and attaches `commitTimestamp`/`commitCount`.
|
|
15
|
+
5. Posts the normalized batch (keyed by `pipelineId`) to the reporting service via `POST /api/reports/events`.
|
|
16
|
+
6. After a successful batch, emits a **delivery-health** signal and **self-heals the dead-letter queue** (Phase 3).
|
|
17
|
+
|
|
18
|
+
CodeBuild `Build State` events are skipped: a build project can be shared across pipelines, so there is no clean 1:1 mapping to a pipeline id.
|
|
19
|
+
|
|
20
|
+
### Tag standard (pipeline-core generates → this forwarder parses)
|
|
21
|
+
|
|
22
|
+
| Tag | Value | Purpose |
|
|
23
|
+
|---|---|---|
|
|
24
|
+
| `pb.pipeline-id` | `<platform pipelineId>` | The platform pipeline id to report against. Pipelines **without** this tag are unregistered and skipped. |
|
|
25
|
+
| `pb.deploys` | `<stage>:<env>` pairs joined by `+`, e.g. `Deploy-stg:staging+Deploy-prod:production` | Declares which stages are deploys and to which environment. CodePipeline-tag-safe (`:` `+` allowed; no JSON). |
|
|
26
|
+
|
|
27
|
+
The forwarder parses `pb.deploys` into a `stage → environment` map. For a `STAGE`/`ACTION` event it sets `environment` **only** when the event's stage matches a key in the map — that (and only that) marks the event as a deploy (`isDeploy` is derived server-side as `environment IS NOT NULL`). `PIPELINE` events have no stage and are never deploys.
|
|
28
|
+
|
|
29
|
+
> No backward compatibility: the old `PIPELINE_EVENT_ID` and `Environment` tags are gone. Already-deployed pipelines produce no DORA data until they re-synth with the new tags.
|
|
30
|
+
|
|
31
|
+
## Data forwarded to the platform
|
|
32
|
+
|
|
33
|
+
The Lambda forwards **only pipeline-execution telemetry** — enough to compute
|
|
34
|
+
success rates, stage/action timing, and DORA metrics. It runs **inside your AWS
|
|
35
|
+
account**; the reporting service only ever receives the normalized payload below.
|
|
36
|
+
|
|
37
|
+
### NOT forwarded (stays in your AWS account)
|
|
38
|
+
|
|
39
|
+
- **AWS account number** — explicitly stripped from every event (`delete detail.account`).
|
|
40
|
+
- **The pipeline ARN** (`arn:aws:codepipeline:<region>:<account>:<name>`) — built only as a
|
|
41
|
+
transient handle to look up the pipeline's `pb.pipeline-id` tag, then discarded; it is
|
|
42
|
+
never stored or sent.
|
|
43
|
+
- **Source-revision URLs** (`revisionUrl`) — read only in-account to classify the source type
|
|
44
|
+
(CodeCommit / GitHub / Bitbucket) for commit-range resolution; not forwarded on their own.
|
|
45
|
+
- **AWS credentials / IAM** and any account-identifying identifiers.
|
|
46
|
+
|
|
47
|
+
The platform stores no AWS account id anywhere (schemas, JWTs, and APIs are account-id-free
|
|
48
|
+
by design), so there is nothing to mask.
|
|
49
|
+
|
|
50
|
+
### Forwarded payload (per event)
|
|
51
|
+
|
|
52
|
+
`POST /api/reports/events` with a batch of:
|
|
53
|
+
|
|
54
|
+
| Field | Type | Notes |
|
|
55
|
+
|---|---|---|
|
|
56
|
+
| `pipelineId` | string | The **platform** pipeline id (from the `pb.pipeline-id` tag) — not the ARN |
|
|
57
|
+
| `eventSource` | `codepipeline` | |
|
|
58
|
+
| `eventType` | `PIPELINE` \| `STAGE` \| `ACTION` | |
|
|
59
|
+
| `status` | enum | The CodePipeline state (`SUCCEEDED`/`FAILED`/…) |
|
|
60
|
+
| `idempotencyKey` | string | Deterministic dedupe key derived from the event's own identity (no PII) |
|
|
61
|
+
| `executionId` | string? | CodePipeline execution GUID |
|
|
62
|
+
| `stageName` / `actionName` | string? | |
|
|
63
|
+
| `errorMessage` | string? | Human-readable failure summary (capped), on failures |
|
|
64
|
+
| `startedAt` / `completedAt` | ISO 8601? | Event timestamps |
|
|
65
|
+
| `durationMs` | number? | |
|
|
66
|
+
| `commitSha` / `commitRef` | string? | Source revision — DORA deploy attribution |
|
|
67
|
+
| `commitTimestamp` | ISO 8601? | Oldest-unshipped commit time for the range since the last deploy — resolved **in-account** (Phase 4). Omitted when unresolvable (reporting falls back to `unknown`) |
|
|
68
|
+
| `commitCount` | number? | Number of commits (≥1) in that range. Omitted when unresolvable |
|
|
69
|
+
| `environment` | string? | Set only when the event's stage is listed in the pipeline's `pb.deploys` tag (⇒ this event is a deploy) |
|
|
70
|
+
| `detail` | object | The raw CodePipeline event detail **with `account` removed** — carries the execution result (log URL, error code) for drill-down |
|
|
71
|
+
|
|
72
|
+
### Commit-range resolution (Phase 4, in-account)
|
|
73
|
+
|
|
74
|
+
For a source/deploy event carrying a `commitSha`, the forwarder resolves the commit timestamp(s) for the range **since the last deploy of that pipeline**, entirely inside your AWS account, per source type detected from the revision URL:
|
|
75
|
+
|
|
76
|
+
- **CodeCommit** → AWS SDK `codecommit:GetCommit` (walks first-parents back to the previous shipped commit).
|
|
77
|
+
- **GitHub / CodeConnections-GitHub** → GitHub REST `compare` / `commits` API. Authenticated with the org's `pipeline-builder/{orgId}/github-token` secret when present (the secret name is derived from `PLATFORM_SECRET_NAME` by swapping the trailing `/platform` for `/github-token`; the value is the raw token string). Falls back to best-effort unauthenticated calls otherwise.
|
|
78
|
+
- **Bitbucket** → Bitbucket REST commit API (single-commit).
|
|
79
|
+
|
|
80
|
+
It emits `commitTimestamp` (oldest unshipped commit) and `commitCount`. Results are cached per commit; SCM rate limits (403/429) trigger a short cooldown; and **any** failure simply omits the fields — commit resolution never fails the batch. The last-shipped commit is tracked in-memory per warm container, so the first deploy after a cold start resolves as a single commit.
|
|
81
|
+
|
|
82
|
+
### Delivery health + self-healing redrive (Phase 3)
|
|
83
|
+
|
|
84
|
+
After a **successful** batch POST, the forwarder (throttled per warm container, best-effort, never failing the batch):
|
|
85
|
+
|
|
86
|
+
1. POSTs a delivery-health signal to `POST /api/reports/ingest-health` `{ forwarded, dropped, lastEventAt }` so the Reports UI can show flowing / stale / dropping. `forwarded` accumulates across batches between health posts; `dropped` is the current DLQ depth snapshot; `lastEventAt` is the newest event timestamp seen.
|
|
87
|
+
2. If the dead-letter queue is non-empty **and** no message-move task is already running, starts an SQS `StartMessageMoveTask` (DLQ → main queue) so retryable failures self-heal without a new AWS service. Guarded: success-gated, one-at-a-time (`ListMessageMoveTasks`), and throttled. Idempotent ingest (`idempotencyKey`) prevents double-counting on redelivery. The DLQ ARN defaults to `<main-queue-arn>-dlq` (derived from the SQS trigger ARN) and can be overridden with `EVENT_DLQ_ARN`.
|
|
88
|
+
|
|
89
|
+
## Key exports
|
|
90
|
+
|
|
91
|
+
| Export | Purpose |
|
|
92
|
+
|---|---|
|
|
93
|
+
| `handler(event: SQSEvent)` | The Lambda entry point. Parses + resolves the SQS batch and POSTs normalized events to the reporting service. |
|
|
94
|
+
|
|
95
|
+
## Runtime
|
|
96
|
+
|
|
97
|
+
- Lambda Node.js runtime, using the runtime-provided `@aws-sdk` clients (`client-codepipeline`, `client-secrets-manager`, and — loaded lazily only when needed — `client-codecommit` and `client-sqs`).
|
|
98
|
+
- Triggered by an SQS queue fed by an EventBridge rule matching the `aws.codepipeline` source; processes events in batches and POSTs them in a single request per invocation.
|
|
99
|
+
- Requires `PLATFORM_BASE_URL` (set by `setup-events`). Optional: `EVENT_DLQ_ARN` (self-healing redrive; defaults to `<main-queue-arn>-dlq`).
|
|
100
|
+
- Authenticates with either `PLATFORM_TOKEN` (a JWT set directly) or `PLATFORM_SECRET_NAME` (a Secrets Manager secret holding the JWT in `password`, created via `pipeline-manager infra store-token`); the resolved token is cached across invocations.
|
|
101
|
+
|
|
102
|
+
### IAM required by this handler
|
|
103
|
+
|
|
104
|
+
The execution role (granted on the events stack — `pipeline-manager/src/templates/events-stack.json`) must allow:
|
|
105
|
+
|
|
106
|
+
| Action | Resource | Used by |
|
|
107
|
+
|---|---|---|
|
|
108
|
+
| `codepipeline:ListTagsForResource` | the pipelines | Tag resolution. An `AccessDenied` here is logged as an error and **fails the batch**, so a missing grant is visible rather than silent. |
|
|
109
|
+
| `secretsmanager:GetSecretValue` | `pipeline-builder/*/platform-*` | Platform JWT (auth). |
|
|
110
|
+
| `secretsmanager:GetSecretValue` | `pipeline-builder/*/github-token-*` | GitHub/Bitbucket commit resolution (Phase 4). Best-effort: absent/denied ⇒ unauthenticated fallback. |
|
|
111
|
+
| `codecommit:GetCommit` | the CodeCommit source repositories | CodeCommit commit resolution (Phase 4). Best-effort. |
|
|
112
|
+
| `sqs:ReceiveMessage`, `sqs:DeleteMessage`, `sqs:GetQueueAttributes` | the main queue | SQS trigger + DLQ depth check. |
|
|
113
|
+
| `sqs:GetQueueAttributes`, `sqs:ListMessageMoveTasks`, `sqs:StartMessageMoveTask` | the **dead-letter queue** | Self-healing redrive (Phase 3). |
|
|
114
|
+
|
|
115
|
+
> The Phase 3/4 actions (`codecommit:GetCommit`, the `github-token` secret read, and the three DLQ `sqs:*` actions) are new grants required by this code — the events-stack IAM owner must add them. All Phase 3/4 paths are best-effort: a missing grant degrades gracefully (fields omitted / redrive skipped) and never fails the batch.
|
|
116
|
+
|
|
117
|
+
## Development
|
|
118
|
+
|
|
119
|
+
```bash
|
|
120
|
+
pnpm build # projen build (compile + lint + test + package)
|
|
121
|
+
pnpm test # run the Jest test suite
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
## License
|
|
125
|
+
|
|
126
|
+
Apache-2.0. See [LICENSE](./LICENSE).
|
package/lib/index.d.ts
ADDED