Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add opt-out import and cclf-import workflows #957

Merged
merged 32 commits into from
Jun 18, 2024
Merged

Conversation

austincanada
Copy link
Contributor

@austincanada austincanada commented Jun 12, 2024

🎫 Ticket

https://jira.cms.gov/browse/BCDA-7899

🛠 Changes

Added cclf-import workflows.
Added Sean's opt-out-import workflows.
Added unit testing workflow for cclf and opt-out workflow.

ℹ️ Context for reviewers

Creating a merge PR in order to test run the workflows. Some things will probably have to change within the workflows themselves.

✅ Acceptance Validation

Workflows completed:
Screenshot 2024-06-18 at 12 23 13 PM
Screenshot 2024-06-18 at 12 23 38 PM

Lambdas updated:
Screenshot 2024-06-18 at 12 29 49 PM

🔒 Security Implications

  • This PR adds a new software dependency or dependencies.
  • This PR modifies or invalidates one or more of our security controls.
  • This PR stores or transmits data that was not stored or transmitted before.
  • This PR requires additional review of its security implications for other reasons.

If any security implications apply, add Jason Ashbaugh (GitHub username: StewGoin) as a reviewer and do not merge this PR without his approval.

gsf and others added 7 commits June 4, 2024 22:22
Updates opt-out import workflows to correctly point to the right
directories.
Adds initial workflow scaffolding to add cclf import lambdas. Actual
deploy scripts will need to be implemented once the lambdas are rolled.
Using PLT-366 workflows, mirror them for cclf-import workflows.
@gsf
Copy link
Member

gsf commented Jun 13, 2024

@austincanada With this PR up, can I close #950?

@austincanada
Copy link
Contributor Author

austincanada commented Jun 13, 2024

@austincanada With this PR up, can I close #950?

@gsf
Yes, that's fine.

aws s3 cp --no-progress ../shared_files/synthetic1800MedicareFiles/test/T\#EFT.ON.ACO.NGD1800.DPRF.D181120.T1000009 \
s3://bfd-test-eft/bfdeft01/bcda/in/T.NGD.DPC.RSP.D$(date +'%y%m%d').T$(date +'%H%M%S')1.IN

# TODO Check bucket for response file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have response files for BCDA, so we'll just want to do the database check below if possible (or maybe just verify that the file was deleted from S3 after being ingested by the app code.)

Will need some arbitrary waiting period / loop or something to allow the lambda to run.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have any examples of us verifying the file was deleted or checking the database? Looking through ab2d and dpc there's no implementation that I can find to mirror them.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No response files? That does change things. Hmm agreed then that the best check would be a job in the workflow to run a self-hosted runner and check the database. Good future work to schedule

@austincanada austincanada merged commit c3baf17 into main Jun 18, 2024
9 checks passed
@austincanada austincanada deleted the austin/BCDA-7899 branch June 18, 2024 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants