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

100496 Throw 500 if any files fail to make it to S3 - IVC CHAMPVA forms #20348

Conversation

michaelclement
Copy link
Contributor

@michaelclement michaelclement commented Jan 17, 2025

Summary

This PR updates the way the IVC CHAMPVA module handles missing uploads when some fail to make it to S3. Previously, the user's submission was allowed to continue if some files failed to make it through. Then steps were taken to manually interpret the submission and determine if enough information made it through.

This created a lot of manual work and room for error. This PR updates the backend so that rather than letting incomplete submissions through, we fail the submission and throw an error that bubbles up to the user. This will prevent users from having a false impression that their submission was acceptable and provides breathing room until the file transmission issue can be worked out.

For more background and context, see this explanation.

Related issue(s)

Testing done

  • New code is covered by unit tests
  • Previously, if some supporting documents didn't make it to S3 a user's submission was allowed to continue
  • See this description for steps on testing
  • If this work is behind a flipper:
    • Tests need to be written for both the flipper on and flipper off scenarios. Docs.
    • What is the testing plan for rolling out the feature?

Screenshots

NA

What areas of the site does it impact?

IVC CHAMPVA forms

Acceptance criteria

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No error nor warning in the console.
  • Events are being sent to the appropriate logging solution
  • Documentation has been updated (link to documentation)
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Feature/bug has a monitor built into Datadog (if applicable)
  • If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
  • I added a screenshot of the developed feature

Requested Feedback

NA

@va-vfs-bot va-vfs-bot temporarily deployed to 100496-change-behavior-of-uploads-controller-so-if-missing-file-exception-occurs-a-500-error-is-returnedshown-to-the-user/main/main January 17, 2025 18:13 Inactive
reiting
reiting previously approved these changes Jan 17, 2025
@va-vfs-bot va-vfs-bot temporarily deployed to 100496-change-behavior-of-uploads-controller-so-if-missing-file-exception-occurs-a-500-error-is-returnedshown-to-the-user/main/main January 17, 2025 22:08 Inactive
@michaelclement michaelclement marked this pull request as ready for review January 21, 2025 14:06
@michaelclement michaelclement requested review from a team as code owners January 21, 2025 14:06
Copy link
Contributor

@cloudmagic80 cloudmagic80 left a comment

Choose a reason for hiding this comment

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

LGTM.

@michaelclement michaelclement merged commit 051e4f3 into master Jan 21, 2025
41 checks passed
@michaelclement michaelclement deleted the 100496-change-behavior-of-uploads-controller-so-if-missing-file-exception-occurs-a-500-error-is-returnedshown-to-the-user branch January 21, 2025 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants