Closed Bipin-dbdigital-in closed 4 months ago
Hi @Bipin-dbdigital-in,
Thanks for filing the issue. The configuration shown appears to be incomplete, do you have a complete example we can reproduce the issue with? I'm also not sure what an aws_config_resource
resource is, as that provider doesn't have any resources by that name. How did you end up with that resource type in your Terraform configuration?
i have one .tf file "resource "aws_guardduty_detector" "f6bb14175c2246c129c79c59" { detector_id = "f6bb14175c2246c129c79c59a" enable = null finding_publishing_frequency = "null" }"
and i want to import it via terraform so i used cmd "terraform import aws_guardduty_detector.f6bb14175c2246c129c79c59 f6bb14175c2246c129c79c59"
so i got the below error
aws_guardduty_detector.f6bb14175c2246c129c79c59: Importing from ID "f6bb14175c2246c129c79c59"... aws_guardduty_detector.f6bb14175c2246c129c79c59: Import prepared! Prepared aws_guardduty_detector for import aws_guardduty_detector.f6bb14175c2246c129c79c59: Refreshing state... [id=f6bb14175c2246c129c79c59] ╷ │ Error: no schema available for aws_config_resource.conf to validate for self-references; this is a bug in Terraform and should be reported │
Thanks @Bipin-dbdigital-in. There must be some trace of the aws_config_resource.conf
in your configuration or state. I don't know where it came from, because I don't think there was ever a resource called that, and I also can't replicate the exact error you are seeing with a nonexistent resource. Can you run a normal terraform plan
and show the output? If you have somehow manually added this resource to your state, you will need to remove it in order to proceed.
Since we have not heard back in a while I'm going to close the issue. If you have any updates regarding the issue, feel free to open a new issue with the requested information. If you have more questions, you can also use the community forum where there are more people ready to help.
Thanks!
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.
Terraform Version
Terraform Configuration Files
Debug Output
Error: no schema available for aws_config_resource.conf to validate for self-references; this is a bug in Terraform and should be reported
Expected Behavior
Error: no schema available for aws_config_resource.conf to validate for self-references; this is a bug in Terraform and should be reported
Actual Behavior
Error: no schema available for aws_config_resource.conf to validate for self-references; this is a bug in Terraform and should be reported
Steps to Reproduce
terraform import aws_glue_catalog_database.mixpanal_dvb $account_id:$databasename
Additional Context
terraform import aws_glue_catalog_database.mixpanal_dvb $account_id:$databasename
References
aws_glue_catalog_database.mixpanel_dvb: Importing from ID "333***:mixpanel_dvb"... aws_glue_catalog_database.mixpanel_dvb: Import prepared! Prepared aws_glue_catalog_database for import aws_glue_catalog_database.mixpanel_dvb: Refreshing state... [id=333**:mixpanel_dvb] ╷ │ Error: no schema available for aws_config_resource.conf to validate for self-references; this is a bug in Terraform and should be reported