NASA-IMPACT / NASA-IMPACT/veda-data
Update pr.yml to use sm2a dag run for publication
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 9
- Forks
- 1
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 1
Description
What
Update automated publish action(s) to use SM2A DAGRun endpoints instead of the legacy workflows dataset/publish endpoint. May require adjustments for auth and will definitely require a slight adjustment to the body posted to the dag run endpoint--for example see this s3 event bridge lambda that submits a request for vector discovery.
AC
-
publish-new-datasetsjob in pr.yml uses sm2a endpoints
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in pr.yml at the publish-new-datasets job and compare its current legacy request with the SM2A DAGRun contract. Read the linked s3_event_bridge_to_sfn_execute/lambda_function.py lines 34-43 for the request body, then inspect the action's authentication handling. Done means the job uses SM2A endpoints for publication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, yaml
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100