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

aws_cognito_user_pool lifecycle crash #26314

Closed
ramimohammad opened this issue Aug 16, 2022 · 3 comments
Closed

aws_cognito_user_pool lifecycle crash #26314

ramimohammad opened this issue Aug 16, 2022 · 3 comments

Comments

@ramimohammad
Copy link

ramimohammad commented Aug 16, 2022

Hello Team ,

required_providers {
aws = {
source = "hashicorp/aws"
version = "4.8.0"
}
}

when we try to add the following

lifecycle {
ignore_changes = [account_recovery_setting]
}
account_recovery_setting {
recovery_mechanism {
name = "admin_only"
priority = 1
}
}

it gives this :
Error: error updating Cognito User pool (eu-central-1_ID): InvalidParameter: 1 validation error(s) found.
│ - minimum field size of 1, UpdateUserPoolInput.AccountRecoverySetting.RecoveryMechanisms.

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Aug 16, 2022
@justinretzolk
Copy link
Member

Hey @ramimohammad 👋 Thank you for taking the time to raise this! So that we have all of the necessary information in order to look into this, can you update the issue description to include all of the information requested in the bug report template?

@justinretzolk justinretzolk added waiting-response Maintainers are waiting on response from community or contributor. and removed needs-triage Waiting for first response or review from a maintainer. labels Aug 17, 2022
@github-actions github-actions bot removed the waiting-response Maintainers are waiting on response from community or contributor. label Oct 19, 2022
@justinretzolk
Copy link
Member

Hey @ramimohammad 👋 Since we haven't heard back, we'll close this issue for now. If you're still having troubles, please feel free to open a new issue and we'll be happy to keep working with you!

@github-actions
Copy link

github-actions bot commented Dec 4, 2022

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants