terraform-provider-awscc
terraform-provider-awscc copied to clipboard
TypeNotFoundException: The type 'AWS::ElastiCache::ServerlessCache' cannot be found
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue 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 issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
- The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.
Terraform CLI and Terraform AWS Cloud Control Provider Version
Affected Resource(s)
Terraform v1.6.6 on windows_386
- provider registry.terraform.io/hashicorp/aws v5.31.0
- provider registry.terraform.io/hashicorp/awscc v0.67.0
- provider registry.terraform.io/hashicorp/cloudinit v2.3.2
- provider registry.terraform.io/hashicorp/external v2.3.2
- provider registry.terraform.io/hashicorp/null v3.2.2
- provider registry.terraform.io/hashicorp/random v3.6.0
- awscc_elasticache_serverless_cache
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
provider "awscc" {
region = "us-east-1"
}
resource "awscc_elasticache_serverless_cache" "ec-svrls" {
engine = "Redis"
serverless_cache_name = "test"
}
Debug Output
Panic Output
Expected Behavior
I expect the ElastiCache to be created
Actual Behavior
Terraform errors with:
awscc_elasticache_serverless_cache.ec-svrls: Creating... ╷ │ Error: AWS SDK Go Service Operation Unsuccessful │ │ with awscc_elasticache_serverless_cache.ec-svrls, │ on main.tf line 5, in resource "awscc_elasticache_serverless_cache" "ec-svrls": │ 5: resource "awscc_elasticache_serverless_cache" "ec-svrls" { │ │ Calling Cloud Control API service CreateResource operation returned: operation error CloudControl: CreateResource, https response │ error StatusCode: 400, RequestID: 6880d2ed-5ec3-4fa1-be40-4240b1c757df, TypeNotFoundException: The type │ 'AWS::ElastiCache::ServerlessCache' cannot be found.
Steps to Reproduce
-
terraform apply
Important Factoids
References
- #0000
Unable to replicate the problem, this could be a transient issue.
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# awscc_elasticache_serverless_cache.ec-svrls will be created
+ resource "awscc_elasticache_serverless_cache" "ec-svrls" {
+ arn = (known after apply)
+ cache_usage_limits = (known after apply)
+ create_time = (known after apply)
+ daily_snapshot_time = (known after apply)
+ description = (known after apply)
+ endpoint = (known after apply)
+ engine = "Redis"
+ final_snapshot_name = (known after apply)
+ full_engine_version = (known after apply)
+ id = (known after apply)
+ kms_key_id = (known after apply)
+ major_engine_version = (known after apply)
+ reader_endpoint = (known after apply)
+ security_group_ids = (known after apply)
+ serverless_cache_name = "test"
+ snapshot_arns_to_restore = (known after apply)
+ snapshot_retention_limit = (known after apply)
+ status = (known after apply)
+ subnet_ids = (known after apply)
+ tags = (known after apply)
+ user_group_id = (known after apply)
}
Plan: 1 to add, 0 to change, 0 to destroy.
awscc_elasticache_serverless_cache.ec-svrls: Creating...
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [10s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [20s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [30s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [40s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [50s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [1m0s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [1m10s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [1m20s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [1m30s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [1m40s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [1m50s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [2m0s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [2m10s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [2m20s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [2m31s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [2m41s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Still creating... [2m51s elapsed]
awscc_elasticache_serverless_cache.ec-svrls: Creation complete after 2m54s [id=test]
@kenroyandfamily can you please try it again and let us know if issue persisted ?