USACE / USACE/chart-docs

[FEAT-API/Lambda]: Build JPM Lambda in API repo

Open
#666 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

  • create the JPM Lambda based off the LCG lambda code. This will include:
    • reviewing and updating the code in screening-tool-api-support/lambda/jpmto ensure the proper script is running and connects to the FEATAPI so it can update the chart_feat.jobs table
    • creating a function in the service layer to invoke the JPM lambda
    • updating the proper JPM handlers to incorporate calling the invoke service
    • passing the proper payload from the data collected
    • anything else I missed
  • Update UI to call the Lambda:
    • update the UI to call the Lambda
    • update the UI poll for the job to be finished and update notification when it is

We should be able to test invoking the Lambda from the UI once this ticket is done

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.

Research direction

Start by reviewing the existing code in screening-tool-api-support/lambda/jpmto and comparing it with the LCG Lambda. Trace the service-layer invocation, JPM handlers, payload flow, and UI polling path; the work is done when the UI can invoke the JPM Lambda, observe completion, and update the notification.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
api, cloud, full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.