fix: use different aws region for cas than us-east-1 #180
Conversation
This file contains 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
smrz2001
force-pushed
the
fix/scheduler-location-constraint
branch
from
7b65f86
to
03466b9
Compare
smrz2001
force-pushed
the
fix/scheduler-location-constraint
branch
from
03466b9
to
4946caa
Compare
smrz2001
force-pushed
the
fix/scheduler-location-constraint
branch
from
4946caa
to
fa61d0d
Compare
auto-merge was automatically disabled
May 21, 2024 16:26
Merge queue setting changed
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.
The CAS Scheduler specifies a location constraint when creating a S3 bucket.
us-east-1is not a valid option when specifying the region.