You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1 error(s) occurred:
* aws_lb_listener_rule.bob-https: 1 error(s) occurred:
* aws_lb_listener_rule.bob-https: Error modifying LB Listener Rule: InvalidLoadBalancerAction: The user pool client must have a client secret
status code: 400, request id: 7dbef1ae-d129-11e8-82fc-61de2e4ad58b
Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
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.
ghost
locked and limited conversation to collaborators
Apr 1, 2020
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Crash Output
terraform plan:
terraform apply:
Error: Error applying plan:
Subsequently, any calls to
terraform plan
(even after reverting changes to the .tf files) result in a crash. Example crash: https://gist.github.com/jmingtan/6eb28f12ac641f5a557d106285b5bbe8Expected Behavior
terraform plan should not crash
Actual Behavior
State seems to be corrupted and I can't run
terraform plan
anymoreThe text was updated successfully, but these errors were encountered: