Fix: Simplify SageMaker artifact handling and update AWS region configuration #93
Conversation
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
added 5 commits
December 5, 2025 10:43
… into sagemaker-e2e-test
… into sagemaker-e2e-test
… into sagemaker-e2e-test
sachinh-amazon
approved these changes
Dec 5, 2025
feiyangliu2023
added a commit
to feiyangliu2023/code-editorv2
that referenced
this pull request
Dec 10, 2025
…guration (aws#93) * fix: use direct artifact filenames without commit-sha in SageMaker workflow --------- Co-authored-by: Feiyang Liu <lfeiyang@amazon.nl>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue
D354258334
The GitHub Actions gh run download command behaves differently when downloading single artifacts, requiring updates to how we handle artifact file paths in the SageMaker workflow. Additionally, the AWS region configuration needed to be updated to us-east-1 for proper SageMaker integration.
Description of Changes
Testing
Rerun testing workflow under sagemaker-e2e-test branch and succeeded
See Smoke Tests for SageMaker #6
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.