Release v7.3.0

[jtherrmann]

TODO:

• Coordinate with @cmarshak regarding the changes from Update ACCESS hyp3 deployment #2293 and release on Fri May 24

Validate for https://hyp3-test-api.asf.alaska.edu:

• API spec changes
• PATCH /user without access_code sets application status to PENDING
• PATCH /user with valid access_code sets application status to APPROVED with correct number of credits and correct access_code field
• 403 responses from PATCH /user for invalid, not yet active, and expired access codes
• submitted job has correct request time

Validate for https://hyp3-enterprise-test.asf.alaska.edu:

• API spec changes
• PATCH /user without access_code sets application status to PENDING
• PATCH /user with valid access_code sets application status to APPROVED with correct number of credits and correct access_code field
• 403 responses from PATCH /user for invalid, not yet active, and expired access codes
• submitted job has correct request time

Validate for https://hyp3-api.asf.alaska.edu:

• API spec changes
• PATCH /user without access_code sets application status to PENDING
• PATCH /user with valid access_code sets application status to APPROVED with correct number of credits and correct access_code field
• 403 responses from PATCH /user for invalid, not yet active, and expired access codes
• submitted job has correct request time

[github-actions]

Developer checklist

• Indicated the level of changes to this package by affixing one of these labels:
  • major -- Major changes to the API that may break current workflows
  • minor -- Minor changes to the API that do not break current workflows
  • patch -- Patches and bugfixes for the current version that do not break current workflows
  • bumpless -- Changes to documentation, CI/CD pipelines, etc. that don't affect the software's version
• (If applicable) Updated the dependencies and indicated any downstream changes that are required
• Added/updated documentation for these changes
• Added/updated tests for these changes
• Verified changes in test deployment and summarized results, e.g. in PR description or comments on the related issue(s)
• If the step function code has changed, have you drained the job queue before merging?
  • For example, if the interface for a Lambda function has changed to expect different input,
    then currently running jobs (which use the old step function definition) will call the new
    function with the old input. So we must drain the job queue before deployment, so that the new
    function is only called by the new step function definition.

Reviewer checklist

• Have all dependencies been updated?
• Is the level of changes labeled appropriately?
• Are all the changes described appropriately in CHANGELOG.md?
• Has the documentation been adequately updated?
• Are the tests adequate?
• Have the changes been verified in the test deployment?

[forrestfwilliams]

All the workshop access codes look good to me, and the changes to HyP3 Access match what is described on the changelog. @jtherrmann and @asjohnston-asf, I'm ready to approve, but will hold off until you two are in the office.

[cmarshak]

@jtherrmann - we are going to leave our zeroed out ACCESS deployment as is. We have very few jobs so we are not in any risk of overrunning our account (we do not need to manually limit the compute environment either). When we need to resume processing, we will coordinate a release to increase the throughput back up again. Thanks for your help and communication on this front.