Skip to content
On PR code update

fix(parser): add aws region to kinesis event #3638

Sign in to view logs

fix(parser): add aws region to kinesis event

fix(parser): add aws region to kinesis event #3638

Triggered via pull request October 25, 2024 20:52
@am29dam29d
synchronize #3260
3227/add-awsregion-to-kinesis-event
Status Success
Total duration 1m 48s
Artifacts –

pr-run-linting-check-and-unit-tests.yml

on: pull_request
run-unit-tests  /  check-layer-publisher
1m 18s
run-unit-tests / check-layer-publisher
run-unit-tests  /  check-docs-snippets
45s
run-unit-tests / check-docs-snippets
run-unit-tests  /  check-docs
47s
run-unit-tests / check-docs
Matrix: run-unit-tests / check-examples
Matrix: run-unit-tests / code-quality
Matrix: run-unit-tests / run-linting-check-and-unit-tests-on-utilities
Fit to window
Zoom out
Zoom in

Annotations

36 errors
run-unit-tests / check-docs-snippets
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-docs-snippets
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/batch)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/batch)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/logger)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/logger)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/idempotency)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/idempotency)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/commons)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/commons)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/idempotency)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/idempotency)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-docs
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-docs
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/jmespath)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/jmespath)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-examples (app)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-examples (app)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/event-handler)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/event-handler)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/commons)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/commons)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/batch)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/batch)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/event-handler)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/event-handler)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/logger)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/logger)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/jmespath)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/jmespath)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-layer-publisher
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-layer-publisher
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / run-linting-check-and-unit-tests-on-utilities (20)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / run-linting-check-and-unit-tests-on-utilities (20)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / run-linting-check-and-unit-tests-on-utilities (18)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / run-linting-check-and-unit-tests-on-utilities (18)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.