Adding decorator to verify submission status

[phildominguez-gsa]

Closes #4436

In this PR:

• Adding a decorator to be applied to view methods (i.e. get, post) to ensure the submission is in the right state before doing any further actions
• If the submission is not in the expected state, it will redirect the user to the submission progress page
• Question: It seems like we don't actually use the certified status anywhere? When it gets to submission, it's still at auditee_certified.

Testing:

• Submissions should still work as normal. Running full-submission should be sufficient to confirm that.
• Get a submission up to the point where the cross validation passes but it's not yet locked.
  • An easy way to do this is comment out lines 95-139 in full-submission.js
• As the auditee (you can set this manually at http://localhost:8000/audit/manage-submission/<report_id>), try to access the URLs below. They should redirect you to the submission progress page because the submission is still "in_progress".
  • Requires auditor_certified: http://localhost:8000/audit/certification/<report_id>
  • Requires auditor_certified: http://localhost:8000/audit/auditee-certification/<report_id>
  • Requires auditor_certified: http://localhost:8000/audit/auditee-certification-confirm/<report_id>
  • Requires auditee_certified: http://localhost:8000/audit/submission/<report_id>
• As the auditor, try to access the URLs below. They should redirect you to the submission progress page because the submission is still "in_progress".
  • Requires ready_for_certification: http://localhost:8000/audit/auditor-certification/<report_id>
  • Requires ready_for_certification: http://localhost:8000/audit/auditor-certification-confirm/<report_id>
• Head to http://localhost:8000/audit/cross-validation/<report_id> to run the cross validation and lock the submission. This will change the status to "ready_for_certification".
• You should now be able to reach http://localhost:8000/audit/auditor-certification/<report_id> and complete the auditor certification. This will change the status to "auditor_certified", making that URL inaccessible again.
• At this point you can complete the submission as the auditee

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 Management Environment #874

[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" = "2024-12-03T19:55:02Z" -> (known after apply)
        }
    }

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

❌ Plan not applied in Deploy to Development and Management Environment #874 (Plan has changed)

[gsa-jrothacker]

what would happen if this look-up fails to find a Single Audit Checklist with that report id?

[phildominguez-gsa]

Good catch, checking for that now

[github-actions]

Package	Line Rate	Branch Rate	Health
.	100%	100%	✔
api	98%	90%	✔
audit	97%	87%	✔
audit.cross_validation	98%	88%	✔
audit.fixtures	84%	50%	❌
audit.intakelib	90%	81%	➖
audit.intakelib.checks	92%	85%	➖
audit.intakelib.common	98%	82%	✔
audit.intakelib.transforms	100%	94%	✔
audit.management.commands	78%	17%	❌
audit.migrations	100%	100%	✔
audit.models	93%	75%	➖
audit.templatetags	100%	100%	✔
audit.views	62%	42%	❌
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	76%	31%	❌
curation	100%	100%	✔
curation.curationlib	57%	100%	❌
curation.migrations	100%	100%	✔
dissemination	91%	72%	➖
dissemination.migrations	97%	25%	✔
dissemination.searchlib	74%	64%	❌
dissemination.templatetags	100%	100%	✔
djangooidc	53%	38%	❌
djangooidc.tests	100%	94%	✔
report_submission	93%	88%	➖
report_submission.migrations	100%	100%	✔
report_submission.templatetags	74%	100%	❌
support	91%	63%	➖
support.management.commands	96%	100%	✔
support.migrations	100%	100%	✔
support.models	97%	83%	✔
tools	98%	50%	✔
users	95%	92%	➖
users.fixtures	100%	83%	✔
users.management	100%	100%	✔
users.management.commands	100%	100%	✔
users.migrations	100%	100%	✔
Summary	91% (17394 / 19214)	76% (2168 / 2842)	➖

[rnovak338]

The manual testing worked perfect for me, nice work.