Skip to content

fix(cognito): cannot use same lambda function as trigger in multiple user pools #22444

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

Merged
merged 3 commits into from
Oct 19, 2022

Conversation

jogold
Copy link
Contributor

@jogold jogold commented Oct 10, 2022

Create the permission in the scope of the user pool
instead of the lambda function.

Integ tests contain destructive changes for the permissions because
of the new logical IDs. This should not cause any downtime since the new permission is created first.

Fixes #22315


All Submissions:

Adding new Unconventional Dependencies:

  • This PR adds new unconventional dependencies following the process described here

New Features

  • Have you added the new feature to an integration test?
    • 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

Sorry, something went wrong.

Verified

This commit was signed with the committer’s verified signature.
bagder Daniel Stenberg
…ools

Create the IAM permission in the scope of the user pool instead of the
lambda function.

Fixes aws#22403
@github-actions github-actions bot added bug This issue is a bug. p2 labels Oct 10, 2022
@aws-cdk-automation aws-cdk-automation requested a review from a team October 10, 2022 14:46
@github-actions github-actions bot added the distinguished-contributor [Pilot] contributed 50+ PRs to the CDK label Oct 10, 2022
@gitpod-io
Copy link

gitpod-io bot commented Oct 10, 2022

Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

@github-actions github-actions bot added the effort/small Small work item – less than a day of effort label Oct 11, 2022
Copy link
Contributor

@corymhall corymhall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for calling our the destructive changes in the integ test!

@corymhall corymhall added the pr-linter/exempt-integ-test The PR linter will not require integ test changes label Oct 18, 2022
@aws-cdk-automation aws-cdk-automation dismissed their stale review October 18, 2022 17:19

✅ Updated pull request passes all PRLinter validations. Dissmissing previous PRLinter review.

@mergify
Copy link
Contributor

mergify bot commented Oct 18, 2022

Thank you for contributing! Your pull request will be updated from main 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: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 945659f
  • 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 b26fc00 into aws:main Oct 19, 2022
@mergify
Copy link
Contributor

mergify bot commented Oct 19, 2022

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

mrgrain pushed a commit to mrgrain/aws-cdk that referenced this pull request Oct 24, 2022
…user pools (aws#22444)

Create the permission in the scope of the user pool 
instead of the lambda function.

Integ tests contain destructive changes for the permissions because
of the new logical IDs. This should not cause any downtime since the new permission is created first.

Fixes aws#22315


----

### All Submissions:

* [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md)

### Adding new Unconventional Dependencies:

* [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies)

### New Features

* [x] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)?
	* [x] 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*
@jogold jogold deleted the cognito-trigger-perm-scope branch November 26, 2022 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. distinguished-contributor [Pilot] contributed 50+ PRs to the CDK effort/small Small work item – less than a day of effort p2 pr-linter/exempt-integ-test The PR linter will not require integ test changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(cognito): permissions for lambda triggers are created in the lambda's scope instead of the user pool's scope
3 participants