Release v10.17.2

[jhkennedy]

Releases fix for user-bucket publishing to project buckets and updates to lavas srg jobs.

user-bucket publishing

"Project" archive bucket publishing (e.g., archive bucket in the same account as the hyp3 deployment) succeeded in LAVAs test:
https://hyp3-lavas-test.asf.alaska.edu/jobs/a0cc7466-b3da-4a90-b6c4-7b839451d135
which has the same_account_publishing: true deployment parameter:

hyp3/.github/workflows/deploy-custom-test.yml

Line 158 in 7d26231

same_account_publishing: true

and failed in a19 test (with no logs as expected):
https://hyp3-a19-jpl-test.asf.alaska.edu/jobs/2d973241-8c81-4480-9875-53d378595208
which has the same_account_publishing: false deployment parameter:

hyp3/.github/workflows/deploy-custom-test.yml

Line 35 in 7d26231

same_account_publishing: false

lavas srg jobs

It works! https://hyp3-lavas-test.asf.alaska.edu/jobs/ae640a70-3b8f-4dcd-89d6-f1622dc88cdc

[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?