Lambda architectures is not updated

Open
#84 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, github-actions, node.js
Domain
ci-cd, cloud

Research direction

Start with the workflow configuration shown in the issue and inspect how appleboy/lambda-action handles the architectures input when deploying an existing Lambda function. Reproduce the deployment with architectures: arm64, then verify the function's configured architecture afterward; done means the deployed function reports arm64 rather than x86.

Written by the indexing model from the issue text.

Description

Current lambda function is on x86 and i want to change it to arm64

      - name: default deploy
        uses: appleboy/lambda-action@master
        with:
          aws_access_key_id: ${{ secrets.AWS_ACCESS_KEY_ID }}
          aws_secret_access_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          aws_region: ap-southeast-1
          function_name: StageTwilloSMS
          zip_file: bundle.zip
          architectures: arm64
          memory_size: 192
          runtime: nodejs18.x
          timeout: 20

after deployment, architecture of the lambda function remain unchanged

Dominant language
D2
Stars
435
Forks
57
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from appleboy/lambda-action

All issues in appleboy/lambda-action

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.