gagoar / invoke-aws-lambda Goto Github PK

Currently both AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY are not treated as secrets within the GitHub workflow ecosystem. This is a security risk that could lead to these being leaked in logs/etc.

This is probably going to be hard to change since existing users probably are not using a specific version of the workflow but rather following the README example and using gagoar/invoke-aws-lambda@master.

Instead of allowing Access keys and secret keys and can we trigger using IAM Role

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: matchPackagePrefixes: matchPackagePrefixes should be inside a 'packageRule' only

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dependency @types/node to v16.18.106
• Update dependency aws-sdk to v2.1686.0
• Update dependency pretty-quick to v3.3.1
• Update dependency tslib to v2.7.0
• Update eslint packages (eslint, eslint-config-prettier)
• Update actions/checkout action to v4
• Update actions/setup-node action to v4
• Update codecov/codecov-action action to v4
• Update dependency husky to v9
• Update dependency lint-staged to v15
• Update dependency node to v20.17.0 (node, @types/node)
• Update dependency prettier to v3
• Update dependency prettier-eslint to v16
• Update dependency pretty-quick to v4
• Update dependency utf-8-validate to v6
• Update dependency ws to v8
• Update eslint packages (major) (eslint, eslint-config-prettier, eslint-plugin-prettier)
• Update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• Update typescript-eslint monorepo to v8 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• Update dependency @actions/core to v1.10.1
• Update dependency bufferutil to v4.0.8
• Update dependency esbuild to v0.23.1
• Update dependency prettier to v2.8.8
• Update typescript-eslint monorepo to v5.62.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency jest to v28.1.3
• Update dependency ts-jest to v28.0.8
• Update dependency utf-8-validate to v5.0.10
• Update actions/setup-node action to v3.8.2
• Update dependency ts-node to v10.9.2
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• Update dependency lint-staged to v10.5.4

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

We using this action:

steps:
      - name: Invoke foobarFunction Lambda
        uses: gagoar/invoke-aws-lambda@master
        with:
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          InvocationType: 'Event'
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          FunctionName: my-trigger
          Payload: ${{ toJson(github) }}

And it works perfect almost for a year.
Just right now we got an error: File not found: '/home/runner/work/_actions/gagoar/invoke-aws-lambda/master/dist/index.js'

Currently when utilizing OpenID instead of the standard Key_ID/Access_key workflow fails with

Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1

would be nice to be able to grab credentials from "aws-actions/configure-aws-credentials@v1" if not using id/key in aws configuration.

Hello,
I have some tests running on aws lambda and lately they've been failing with the following message:

Run gagoar/[email protected] with: FunctionName: BackendTests REGION: eu-west-1 AWS_ACCESS_KEY_ID: *** AWS_SECRET_ACCESS_KEY: *** SUCCEED_ON_FUNCTION_FAILURE: false MAX_RETRIES: 0 HTTP_TIMEOUT: 12000000 LogType: Tail Payload: [{"suite": "shipments","verbose": true},{"suite": "shipment-list","verbose": true},{"suite": "shipment-api","verbose": true}] InvocationType: RequestResponse Error: read ECONNRESET
This error seems to happen after around 4-5 minutes even though I set HTTP_TIMEOUT to a very high number and my tests are passing.