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

Add configuration set support for Cognito user pools #16749

Closed
wants to merge 2 commits into from
Closed

Add configuration set support for Cognito user pools #16749

wants to merge 2 commits into from

Conversation

johngallagher
Copy link
Contributor

Adds configuration set support for Cognito user pools.

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Release note for CHANGELOG:

* resource/aws_cognito_user_pool: Add `configuration_set`

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAWSCognitoUserPool_withEmailConfiguration'                                                                                                  

==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -count 1 -parallel 20 -run=TestAccAWSCognitoUserPool_withEmailConfiguration -timeout 120m
=== RUN   TestAccAWSCognitoUserPool_withEmailConfiguration
=== PAUSE TestAccAWSCognitoUserPool_withEmailConfiguration
=== CONT  TestAccAWSCognitoUserPool_withEmailConfiguration
--- PASS: TestAccAWSCognitoUserPool_withEmailConfiguration (49.71s)
PASS
ok      github.com/terraform-providers/terraform-provider-aws/aws       52.910s

@johngallagher johngallagher requested a review from a team as a code owner December 14, 2020 13:41
@ghost ghost added size/S Managed by automation to categorize the size of a PR. documentation Introduces or discusses updates to documentation. service/cognito tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. labels Dec 14, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Dec 14, 2020
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Welcome @johngallagher 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.

Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.

Thanks again, and welcome to the community! 😃

Base automatically changed from master to main January 23, 2021 00:59
@YakDriver YakDriver self-assigned this Feb 25, 2021
@YakDriver YakDriver removed the needs-triage Waiting for first response or review from a maintainer. label Feb 25, 2021
@YakDriver
Copy link
Member

@johngallagher @simplybusiness Thank you for your work on this PR! I will be working on this before long. In order to expedite the process, I will likely make some changes. Make sure that you have checked the box "Allow edits from maintainers." (Don't worry though, you will receive all credit for your contribution and code!) Also, please coordinate with us before making any commits to this branch. Again, thank you for your help and we look forward to this popular addition to the AWS provider!

@YakDriver YakDriver added the waiting-response Maintainers are waiting on response from community or contributor. label Feb 25, 2021
@johngallagher
Copy link
Contributor Author

@YakDriver Thanks! Sorry for the delay - I've been off work for a few weeks. I followed the instructions on Github to do this but the tickbox doesn't appear for me where it says it should on this PR page.

Let me know if I've done something wrong or if there's something else you need from me. Thanks.

@ghost ghost removed waiting-response Maintainers are waiting on response from community or contributor. labels Mar 1, 2021
@YakDriver
Copy link
Member

@johngallagher Thanks for getting back to me. The problem is that @simplybusiness owns the repository that owns the fork that you requested to be pulled. SB will need to check that box. Another option is for me to create a separate branch and cherry pick your commits from this fork. You'll get credit as though it was your PR. Are you in contact with SB?

@YakDriver YakDriver added the waiting-response Maintainers are waiting on response from community or contributor. label Mar 4, 2021
@johngallagher
Copy link
Contributor Author

@johngallagher Thanks for getting back to me. The problem is that @simplybusiness owns the repository that owns the fork that you requested to be pulled. SB will need to check that box. Another option is for me to create a separate branch and cherry pick your commits from this fork. You'll get credit as though it was your PR. Are you in contact with SB?

Yup, I still work there. So I'll ask for an admin to enable this... thanks for your patience!

@ghost ghost removed waiting-response Maintainers are waiting on response from community or contributor. labels Mar 5, 2021
@johngallagher
Copy link
Contributor Author

johngallagher commented Mar 5, 2021

@johngallagher Thanks for getting back to me. The problem is that @simplybusiness owns the repository that owns the fork that you requested to be pulled. SB will need to check that box. Another option is for me to create a separate branch and cherry pick your commits from this fork. You'll get credit as though it was your PR. Are you in contact with SB?

@YakDriver - I've asked an admin to look at this and they can't see the tickbox either. Sorry!

So yeah, if you could create a separate branch and cherry pick commits, that'd be great. Sorry for the hassle!

@YakDriver
Copy link
Member

@johngallagher It's the second time I've run into this recently with contributors that do not own their forks. Perhap it's a GitHub limitation or it is influenced by a @simplybusiness organization-level setting.

@johngallagher
Copy link
Contributor Author

@johngallagher It's the second time I've run into this recently with contributors that do not own their forks. Perhap it's a GitHub limitation or it is influenced by a @simplybusiness organization-level setting.

My bet is that SB have disabled something at a high level even for admins. Cherry pick away and sorry again for the hassle.

@YakDriver
Copy link
Member

@johngallagher You can see your contribution as part of #14935! Thanks again. 🎉

@ghost
Copy link

ghost commented Mar 12, 2021

This has been released in version 3.32.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

@ghost
Copy link

ghost commented Apr 8, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Apr 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Introduces or discusses updates to documentation. size/S Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants