Skip to content

[ELI-688] - Adding Kinesis Data Stream as a buffer for Firehose #3250

[ELI-688] - Adding Kinesis Data Stream as a buffer for Firehose

[ELI-688] - Adding Kinesis Data Stream as a buffer for Firehose #3250

Triggered via pull request March 18, 2026 21:30
Status Failure
Total duration 2m 54s
Artifacts 4

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
4s
Set CI/CD metadata
Commit stage  /  Scan secrets
11s
Commit stage / Scan secrets
Commit stage  /  Check file format
9s
Commit stage / Check file format
Commit stage  /  Check Markdown format
4s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
11s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
6s
Commit stage / Lint Terraform
Commit stage  /  Checkov Terraform
37s
Commit stage / Checkov Terraform
Commit stage  /  Count lines of code
9s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
44s
Commit stage / Scan dependencies
Commit stage  /  OWASP Dependency Scan
37s
Commit stage / OWASP Dependency Scan
Commit stage  /  Check for dead code
32s
Commit stage / Check for dead code
Test stage  /  Linting
32s
Test stage / Linting
Test stage  /  Unit tests
58s
Test stage / Unit tests
Test stage  /  Perform static analysis
56s
Test stage / Perform static analysis
Build stage  /  Lambda Artefact
Build stage / Lambda Artefact
Acceptance stage  /  Environment set up
Acceptance stage / Environment set up
Acceptance stage  /  Accessibility test
Acceptance stage / Accessibility test
Acceptance stage  /  Contract test
Acceptance stage / Contract test
Acceptance stage  /  Integration test
Acceptance stage / Integration test
Acceptance stage  /  Load test
Acceptance stage / Load test
Acceptance stage  /  Security test
Acceptance stage / Security test
Acceptance stage  /  UI performance test
Acceptance stage / UI performance test
Acceptance stage  /  UI test
Acceptance stage / UI test
Acceptance stage  /  Environment tear down
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
Test stage / Linting
Process completed with exit code 2.
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Commit stage / OWASP Dependency Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: github/codeql-action/upload-sarif@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Commit stage / OWASP Dependency Scan
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
coverage.xml
7.15 KB
sha256:87923eb173cd27e0716cbaf6447fbacd93f19a260d75142b85303b63c6189f99
lines-of-code-report-.json.zip Expired
846 Bytes
sha256:445bad42e70d11decea77ed2db19224395919312dca6390b9bbecbf949e8813a
sbom-repository-report.json.zip Expired
58.7 KB
sha256:cfc43b5938d05bd140c597525051502d3020fff4d1c32248408a75519819ad78
vulnerabilities-repository-report-.json.zip Expired
5.7 KB
sha256:3218a2b383600ae2a8b8a10d11c64c1643775a9e9ef114ddfab70b23dc0889d3