Skip to content
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(codepipeline): detect the account of the Action from its backing resource's account, not its Stack's account #14224

Merged

Conversation

skinny85
Copy link
Contributor

In CodePipeline, Actions can have a resource backing it (like an S3 Bucket, or an ECS Service).
In the CodePipeline construct however,
the account a given action was in was incorrectly determined by checking the Stack of the backing resource,
instead of the resource itself.
This value can be different for imported resources.

Fixes #14165


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

…resource's account, not its Stack's account

In CodePipeline, Actions can have a resource backing it (like an S3 Bucket, or an ECS Service).
In the CodePipeline construct however,
the account a given action was in was incorrectly determined by checking the Stack of the backing resource,
instead of the resource itself.
This value can be different for imported resources.

Fixes aws#14165
@skinny85 skinny85 requested a review from rix0rrr April 16, 2021 21:39
@gitpod-io
Copy link

gitpod-io bot commented Apr 16, 2021

@mergify
Copy link
Contributor

mergify bot commented Apr 19, 2021

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).

@mergify
Copy link
Contributor

mergify bot commented Apr 19, 2021

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-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: ceb2fc3
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit d88e915 into aws:master Apr 19, 2021
@skinny85 skinny85 deleted the fix/codepipeline-cross-account-backing-resource branch April 19, 2021 15:05
hollanddd pushed a commit to hollanddd/aws-cdk that referenced this pull request Aug 26, 2021
…resource's account, not its Stack's account (aws#14224)

In CodePipeline, Actions can have a resource backing it (like an S3 Bucket, or an ECS Service).
In the CodePipeline construct however,
the account a given action was in was incorrectly determined by checking the Stack of the backing resource,
instead of the resource itself.
This value can be different for imported resources.

Fixes aws#14165

----

*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
Labels
@aws-cdk/aws-codepipeline Related to AWS CodePipeline contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

code-pipeline: Existing S3 buckets are not given the correct permissions
3 participants