-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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 aws_cognito_user resource #19919
Conversation
Only user-attributes are currently supported
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @rtim75 👋
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! 😃
Another thing I'm not sure about is I'm thinking about adding it with |
Any status update on this? |
Hey, as you probably have noticed I've been working very slowly on this one. I will try to finish at least the main resource( |
Renamed resource to aws_cognito_user_pool_user PR: hashicorp#19919 Issue: hashicorp#4542
ea30815
to
d9a7743
Compare
TODO:
|
@rtim75 in case you were unaware, it looks like updating the changelog is required per PR guidelines changelog process. Just in case you were unaware of this I wanted to point it out since I didn't see it explicitly on the TODO list. Thanks for all your work on this! |
Testing of the client-side arguments can get challenging, since many of them are handled by a Lambda function that's a part of an authentication/authorization system, and it could be implementation-dependent. For the most part, we rely on the AWS API catching major errors. For implementation in Terraform, in general we try to match the AWS API structures. Sometimes this can end up looking a little strange, like the MFA information. However, it makes dealing with changes on the AWS side easier, for example if they added another MFA contact method, they could just add an item to the list, instead of needing to add another Boolean parameter. |
For the timestamp fields, I would include them for consistency with the other resources. |
7ac1886
to
1952176
Compare
This ensures that the attributes array is fully saved in state while suppressing changes to delete the "sub" attribute, which all cognito users have.
@gdavison The PR is ready for the second review. All the discussions have been resolved. The only failing action is caused by resources unrelated to this PR. |
Gentle ping @gdavison :) We desperately need this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! 🚀
--- PASS: TestAccCognitoUser_disappears (40.50s)
--- PASS: TestAccCognitoUser_basic (46.74s)
--- PASS: TestAccCognitoUser_enabled (68.43s)
--- PASS: TestAccCognitoUser_attributes (69.27s)
--- PASS: TestAccCognitoUser_password (86.09s)
--- PASS: TestAccCognitoUser_temporaryPassword (86.16s)
Thanks so much @rtim75 for adding this! I'm looking forward to being able to use this soon! |
This functionality has been released in v4.0.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. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #4542
Output from acceptance testing: