Open joelzhuang opened 2 years ago
Have the same issue, we're urgent in our project to implement this, could someone please help? Thanks
When creating a bot without slots, it's fast, less than 30 seconds. Then after adding 1 slot, terraform validate
turns to very slow, took several minutes, terraform apply
is only showing this after ~10 minutes
awscc_lex_bot.demo_lexv2_bot: Refreshing state... [id=4H7KKR8QAY]
Is there an update on this ticket. No assignees to this ticket still
I had something similar, the deploy time was not hour but still 5 minutes for a simple change or so, and during Refreshing state CPU usage of terraform-awscc-provider went up to 140%... macOS 12.5
Having very similar issues. Deploy terraform a lot with no issues. Started using the AWSCC provider to deploy a Lex bot. Facing very long state refresh times and sporadically long deploy times. Any update on this issue? Would love to know if I should just stop using it for now?
Trying to decide whether the project should start using the AWSCC provider for other resource deployments.
Same thing here.
I decided to just replace awscc
with a regular aws_cloudformation_stack
resource and write it all inside a jsonencode()
since LexV2 can be deployed that way too, and it's a lot faster at determining the differences.
Community Note
Terraform CLI and Terraform AWS Cloud Control Provider Version
Terraform v1.2.2 on linux_amd64
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Note: I've created another issue regarding why I added slots to the fallback intent https://github.com/hashicorp/terraform-provider-awscc/issues/547
Expected Behavior
Deploy the LexV2 bot within a reasonable timeframe (minutes)
Actual Behavior
LexV2 bot with 2 intents, one custom slot type and one slot takes more than an hour to deploy, often resulting in an error at the end, either because the credentials expire, or the error mentioned above.
It seems the deployment takes a long time after the slots attribute is added to the intent. (I've also done tests with slot_types without slots, and it deploys fine)
Steps to Reproduce
terraform apply
0000