Simpler csv dump

[jadudm]

Addresses #5227

In this PR

• Replaces the sling-based CSV dumper with a bash-based dumper.
• Runs in ~15 minutes in production-like environments (compared to a few hours for the sling dumper).
• This will replace the old dumper in the GH workflow

Testing

This can be tested locally. It was tested w/ @asteel-gsa and @jperson1 as reviewers in preview and staging, and we see full E2E for dump->S3, and links route correctly from static.

Local testing:

• Have some local data
• cd backend
• The Dockerfile has a new unzip install, so make docker-first-run && docker compose up
• docker compose exec web /bin/bash
• ENV=LOCAL ./util/csv-export-to-s3/csv-export-to-s3.bash
• This should be populated with the generated CSVs: http://localhost:9002/browser/gsa-fac-private-s3/public-data%2Fgsa%2F

PR Checklist: Submitter

• Link to an issue if possible. If there’s no issue, describe what your branch does. Even if there is an issue, a brief description in the PR is still useful.
• List any special steps reviewers have to follow to test the PR. For example, adding a local environment variable, creating a local test file, etc.
• For extra credit, submit a screen recording like this one.
• Make sure you’ve merged main into your branch shortly before creating the PR. (You should also be merging main into your branch regularly during development.)
• Make sure you’ve accounted for any migrations. When you’re about to create the PR, bring up the application locally and then run git status | grep migrations. If there are any results, you probably need to add them to the branch for the PR. Your PR should have only one new migration file for each of the component apps, except in rare circumstances; you may need to delete some and re-run python manage.py makemigrations to reduce the number to one. (Also, unless in exceptional circumstances, your PR should not delete any migration files.)
• Make sure that whatever feature you’re adding has tests that cover the feature. This includes test coverage to make sure that the previous workflow still works, if applicable.
• Make sure the full-submission.cy.js Cypress test passes, if applicable.
• Do manual testing locally. Our tests are not good enough yet to allow us to skip this step. If that’s not applicable for some reason, check this box.
• Verify that no Git surgery was necessary, or, if it was necessary at any point, repeat the testing after it’s finished.
• Once a PR is merged, keep an eye on it until it’s deployed to dev, and do enough testing on dev to verify that it deployed successfully, the feature works as expected, and the happy path for the broad feature area (such as submission) still works.
• Ensure that prior to merging, the working branch is up to date with main and the terraform plan is what you expect.

PR Checklist: Reviewer

• Pull the branch to your local environment and run make docker-clean; make docker-first-run && docker compose up; then run docker compose exec web /bin/bash -c "python manage.py test"
• Manually test out the changes locally, or check this box to verify that it wasn’t applicable in this case.
• Check that the PR has appropriate tests. Look out for changes in HTML/JS/JSON Schema logic that may need to be captured in Python tests even though the logic isn’t in Python.
• Verify that no Git surgery is necessary at any point (such as during a merge party), or, if it was, repeat the testing after it’s finished.

The larger the PR, the stricter we should be about these points.

Pre Merge Checklist: Merger

• Ensure that prior to approving, the terraform plan is what we expect it to be. -/+ resource "null_resource" "cors_header" should be destroying and recreating its self and ~ resource "cloudfoundry_app" "clamav_api" might be updating its sha256 for the fac-file-scanner and fac-av-${ENV} by default.
• Ensure that the branch is up to date with main.
• Ensure that a terraform plan has been recently generated for the pull request.

[github-actions]

Terraform plan for meta

No changes. Your infrastructure matches the configuration.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

✅ Plan applied in Deploy to Development and Meta Environments #1159

[github-actions]

Terraform plan for dev

Plan: 1 to add, 0 to change, 1 to destroy.

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # module.dev.module.cors.null_resource.cors_header must be replaced
-/+ resource "null_resource" "cors_header" {
!~      id       = "******************" -> (known after apply)
!~      triggers = { # forces replacement
!~          "always_run" = "2026-04-09T22:27:29Z" -> (known after apply)
        }
    }

Plan: 1 to add, 0 to change, 1 to destroy.

❌ Plan not applied in Deploy to Development and Meta Environments #1159 (Plan has changed)

[asteel-gsa]

Approved.

Tested this on call in both preview and staging. ~15 min run time compared to current csv export (7.5h)

[jadudm]

Before this ships, if it is not too difficult, it would be good to include a dump of combined. Given that it is an MV, and it is a JOIN across tables that are guaranteed to be public (double check), it might be possible to do a SELECT * against the dissemination_combined table and export it wholesale as well.

This would be valuable for upstream consumers of the data. We have some Federal partners who are pulling the CSVs as an import, and having to compute the JOINs on their end is not fun. Given that we have already computed the join, if we export the table as part of this simpler dump process, it's a win for everyone.

It will require an update to the public pages (so we link to the combined CSV), but it should be a straight-forward add.

[github-actions]

Package	Line Rate	Branch Rate	Health
.	100%	100%	✔
api	98%	86%	✔
api.serializers	97%	88%	✔
api.views	91%	96%	✔
audit	95%	80%	✔
audit.cross_validation	97%	86%	✔
audit.fixtures	84%	50%	❌
audit.formlib	92%	62%	✔
audit.intakelib	89%	83%	➖
audit.intakelib.checks	92%	86%	✔
audit.intakelib.common	98%	82%	✔
audit.intakelib.transforms	100%	95%	✔
audit.management.commands	78%	17%	❌
audit.migrations	100%	100%	✔
audit.models	91%	68%	✔
audit.templatetags	100%	100%	✔
audit.test_viewlib	100%	100%	✔
audit.views	75%	52%	❌
census_historical_migration	96%	65%	✔
census_historical_migration.migrations	100%	100%	✔
census_historical_migration.sac_general_lib	92%	84%	✔
census_historical_migration.transforms	95%	90%	✔
census_historical_migration.workbooklib	68%	69%	❌
config	78%	37%	❌
curation	98%	100%	✔
curation.curationlib	88%	72%	➖
curation.migrations	100%	100%	✔
dissemination	90%	69%	✔
dissemination.analytics	27%	0%	❌
dissemination.forms	80%	30%	❌
dissemination.migrations	97%	25%	✔
dissemination.models	100%	100%	✔
dissemination.report_generation	21%	0%	❌
dissemination.report_generation.excel	32%	0%	❌
dissemination.searchlib	61%	43%	❌
dissemination.templatetags	52%	6%	❌
dissemination.views	67%	47%	❌
djangooidc	53%	38%	❌
djangooidc.tests	100%	94%	✔
report_submission	100%	96%	✔
report_submission.migrations	100%	100%	✔
report_submission.templatetags	74%	100%	❌
report_submission.views	77%	61%	❌
support	94%	75%	✔
support.migrations	100%	100%	✔
support.models	90%	50%	➖
tools	98%	50%	✔
users	95%	86%	✔
users.fixtures	100%	83%	✔
users.management	100%	100%	✔
users.management.commands	100%	100%	✔
users.migrations	100%	100%	✔
Summary	89% (22134 / 24966)	69% (2703 / 3922)	➖

Minimum allowed line rate is 85%

[jperson1]

Tested manually once more in Preview, and moving forward with confidence in the scheduled command in the lower environments.