Fix regional validation errors in London CloudWatch alarms#3910
Open
davidgisbey wants to merge 1 commit intomainfrom
Open
Fix regional validation errors in London CloudWatch alarms#3910davidgisbey wants to merge 1 commit intomainfrom
davidgisbey wants to merge 1 commit intomainfrom
Conversation
davidgisbey
force-pushed
the
add-aliased-aws-provider
branch
from
f0c0409 to
d571186
Compare
I've tried to add a new aws_sns_topic with the "eu-west-2", but i'm still getting failures when i try to apply the changes. I suspect it's using the default provider at some point, which is configured with the "eu-west-1" region. My hope is that by adding an aliased provider with the "eu-west-2" region, we can ensure that the correct provider is used for the new resources.
davidgisbey
force-pushed
the
add-aliased-aws-provider
branch
from
6bd6de8 to
678c281
Compare
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
1 participant
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.
Description
Use aliased AWSprovider with "eu-west-2" region
I've tried to add a new aws_sns_topic with the "eu-west-2", but i'm still
getting failures when i try to apply the changes.
I suspect it's using the default provider at some point, which is
configured with the "eu-west-1" region.
My hope is that by adding an aliased provider with the "eu-west-2" region,
we can ensure that the correct provider is used for the new resources.