Introduction#

If you’re working with Azure, you might have encountered an error that looks something like this:

“Failure sending request: StatusCode=0 — Original Error: Code=‘ReferencedResourceNotProvisioned’ Message=‘Cannot proceed with operation because resource used by resource is not in Succeeded state. Resource is in Updating state and the last operation that updated/is updating the resource is PutSubnetOperation.’”

Though the error message can seem intimidating and cryptic at first, don’t worry. In this post, we’ll delve into what this error means and how you can resolve it.

The example below will import an AWS instance into a terraform module:

terraform import module.foo.aws_instance.bar i-abcd1234

In the realm of Infrastructure as Code, Terraform modules can play a significant role in making your life easier. Sometimes, however, these modules don’t live at the root directory of their source package. Instead, they reside in sub-directories. Thankfully, Terraform has a smart way to help you access these nested modules.

Terraform employs a unique double-slash (//) syntax to help pinpoint the exact sub-directory where the module is located. The path that follows this double-slash syntax is considered to be a sub-directory within the package or repository.