375 add parameter to build and run model res workflow to run ingest on batch

[Damonamajor]

This currently errors out on dev branches. Is it worth it to provide permissions for all dev branches to ensure new features can be added without them going into our main datalake?

A test was run by removing prox_nearest_metra_route_dist_ft as an input variable in the ingest script. As desired, it returned null values in assessment_card

SELECT
meta_pin, prox_nearest_metra_route_dist_ft
from assessment_card
where run_id = '2025-05-29-agitated-sam'
limit 10

Final run with up to date changes
https://github.com/ccao-data/model-res-avm/actions/runs/15330192847

[Damonamajor]

This is needed to install renv::igraph

[jeancochrane]

[Praise] Nice catch!

[Damonamajor]

It errors without this when run through actions and doesn't seem to do anything when run locally.

[jeancochrane]

[Praise] Yup, this is right! It doesn't error out locally in the absence of this param because we instruct team members to set the AWS_ATHENA_S3_STAGING_DIR env var in their root-level .Renviron file, which Noctua knows to use as a fallback. Setting this parameter directly in the dbConnect() function will override that root-level environment variable when we run this script locally, but I think it's fine because we rarely change this query location.

[jeancochrane]

Nice work getting this over the line! I've tested workflows myself both with and without repro_ingest and it seems to work correctly both ways.

[jeancochrane]

[Praise] Nice catch!

[jeancochrane]

[Praise] Yup, this is right! It doesn't error out locally in the absence of this param because we instruct team members to set the AWS_ATHENA_S3_STAGING_DIR env var in their root-level .Renviron file, which Noctua knows to use as a fallback. Setting this parameter directly in the dbConnect() function will override that root-level environment variable when we run this script locally, but I think it's fine because we rarely change this query location.