-
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
fix(cloudfront): EdgeFunction us-east-1 stack created in different account #13055
Conversation
…count The us-east-1 stack for EdgeFunction was defaulting to the default deploy account. This means that using one account to deploy, and another for the stack which contains the EdgeFunction, the support stack in us-east-1 will be deployed into the deploy account, rather than stack account. This fix has the us-east-1 stack inherit the account from the parent stack. fixes #12789
packages/@aws-cdk/aws-cloudfront/test/experimental/edge-function.test.ts
Show resolved
Hide resolved
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
…count (aws#13055) The us-east-1 stack for EdgeFunction was defaulting to the default deploy account. This means that using one account to deploy, and another for the stack which contains the EdgeFunction, the support stack in us-east-1 will be deployed into the deploy account, rather than stack account. This fix has the us-east-1 stack inherit the account from the parent stack. fixes aws#12789 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The us-east-1 stack for EdgeFunction was defaulting to the default deploy
account. This means that using one account to deploy, and another for the stack
which contains the EdgeFunction, the support stack in us-east-1 will be deployed
into the deploy account, rather than stack account.
This fix has the us-east-1 stack inherit the account from the parent stack.
fixes #12789
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license