[APP-345] feat: sas, scriptifying test harness for use outside of tests

[mcmcgrath13]

Description

• Make test harness for loading fake data also available via script
• Add SAS container to build options
• Simplify API for using the table faker harness

Notes:

• Purposefully keeping the details on the SAS container in NEDSS Dev as it is private and you need access there to use it
• Needed for these instructions on comparison testing to work

Tickets

• https://cdc-nbs.atlassian.net/browse/APP-384

Checklist before requesting a review

• PR focuses on a single story
• Code has been fully tested to meet acceptance criteria
• PR is reasonably small and reviewable (Generally less than 10 files and 500 changed lines)
• All new functions/classes/components reasonably small
• Functions/classes/components focused on one responsibility
• Code easy to understand and modify (clarity over concise/clever)
• PRs containing TypeScript follow the Do's and Don'ts
• PR does not contain hardcoded values (Uses constants)
• All code is covered by unit or feature tests

[JordanGuinn]

One q about a potential env gate for the data scripts, but otherwise looks good to me! 🚀

[JordanGuinn]

(thought, b): Are there any build parameters or env vars we can take advantage of here to ensure this and the restore_original.data.py can only ever be run in dev/pre-prod environments?

[mcmcgrath13]

These files (scripts or tests) aren't included in our built container, which I think is our best proxy for prod. Given a human would need to set up an env var for the connection to a prod database, then also pass an argument, it feels like it would need to be pretty intentional. And the good news is they could maybe quickly restore if they did this by accident?

I don't think there's any way to know from a DB itself if it's production or not 🤔

[JordanGuinn]

Alrighty. Something to keep an eye on moving forward I'd think, should we ever expand usage of that env var, or need to incorporate any Python scripts into the build for whatever reason

[JordanGuinn]

TIL that the therestore_original_data call after the yield indicates to pytest that it's teardown code! For a sec I was confused as to why we were inserting fake data just to immediately truncate it 😅 🤦

[emyl3]

worked as expected for me!