-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws-appsync: imported resources from other regions using the current stack region #20195
Labels
Comments
ryanvaloris
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
May 3, 2022
4 tasks
RomainMuller
added
p1
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
May 3, 2022
related #13691 |
mergify bot
pushed a commit
that referenced
this issue
May 5, 2022
…20193) Replaces all uses of `resource.stack.region` with `resource.env.region` so that imported resources can provide a different region than the current stack, wich can result in invalid configuration. Applying the same treatment to occurrences of `resources.stack.account` as this is also surfaced as `resources.env.account`. Fixes #20195 ---- ### All Submissions: * [X] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/master/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
wphilipw
pushed a commit
to wphilipw/aws-cdk
that referenced
this issue
May 23, 2022
…ws#20193) Replaces all uses of `resource.stack.region` with `resource.env.region` so that imported resources can provide a different region than the current stack, wich can result in invalid configuration. Applying the same treatment to occurrences of `resources.stack.account` as this is also surfaced as `resources.env.account`. Fixes aws#20195 ---- ### All Submissions: * [X] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/master/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When trying to import a Cognito UserPool to be used in an AppSync Graphql domain, the UserPool is configured with the region of the stack that is being deployed and disregards the region supplied in the ARN.
Expected Behavior
Using the construct below and assuming that
this.stack
is created inus-west-2
:I expected the UserPool to be linked to the UserPool created in
us-east-1
per the ARN provided.Current Behavior
However, the generated output shows
us-west-2
as the region:Reproduction Steps
build a new graphQl API with a UserPool from a different region
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
1.152.0
Framework Version
No response
Node.js Version
v16.10.0
OS
MacOS Monterey 12.3
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: