Can't specify Subnet and Security group.. Whats missing ?

Open
#81 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, github-actions
Domain
cloud, devops

Research direction

Start with the attached source configuration and the deployment inputs documented by lambda-action, then compare how subnet and security-group values are passed to AWS Lambda. Reproduce the reported configuration and trace the action output to identify what is missing. Done means a documented configuration successfully updates a Lambda function with both settings.

Written by the indexing model from the issue text.

Description

          @appleboy 

Attached source config..
Screenshot 2024-06-11 at 1 33 27 pm
Screenshot 2024-06-11 at 1 28 52 pm

Please help me to find whats wrong

Originally posted by @Minu2020 in https://github.com/appleboy/lambda-action/issues/76#issuecomment-2159715079

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 Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.