Updates to user defined buckets #3102
Merged
Merged
Conversation
…gs in step function
jhkennedy
commented
May 19, 2026
| @@ -1,4 +1,5 @@ | |||
| boto3==1.42.97 | |||
| pydantic==2.12.5 | |||
Contributor
Author
There was a problem hiding this comment.
This was needed because a different version kept getting installed and uploaded, which pip was warning about...
I'd like to test removing all these after we merge to test, because we really shouldn't need to specify them.
AndrewPlayer3
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was able to deploy this branch to https://hyp3-jhk-sandbox.asf.alaska.edu/ and run a few burst jobs that write their files to a private bucket in the LAVAs account, as well as a couple autorift jobs that failed expectedly to check the failure path as well.
The example jobs:
https://hyp3-jhk-sandbox.asf.alaska.edu/jobs?name=test-user-bucket&user_id=jhkennedy
or
This PR:
sts.get_caller_identity()usage for JSON output from AWS APIs{job_id}.logirrespective of the bucket and bucket_prefix providedRef::bucketRef::bucket_prefixinstead of! Ref bucketandRef::job_idWith these changes, I think we're ready to merge to develop and take it for a spin in a broader set of environments, particularly EDC.