From a0832b9886b249f0b9a155832208dc2d28061d9c Mon Sep 17 00:00:00 2001 From: Sathija Pavuluri Date: Tue, 7 Apr 2020 20:36:02 -0400 Subject: [PATCH] website: In import usage doc, use aws_network_acl as an example of complex import with secondary resources (#24525) A proposed pull request to the AWS provider would change the import behavior of `aws_security_group`. This preemptive change will help keep the docs accurate if that gets merged. --- website/docs/import/usage.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/import/usage.html.md b/website/docs/import/usage.html.md index 717635a77..37a75105b 100644 --- a/website/docs/import/usage.html.md +++ b/website/docs/import/usage.html.md @@ -64,8 +64,8 @@ align with the current (or desired) state of the imported object. The above import is considered a "simple import": one resource is imported into the state file. An import may also result in a "complex import" where -multiple resources are imported. For example, an AWS security group imports -an `aws_security_group` but also one `aws_security_group_rule` for each rule. +multiple resources are imported. For example, an AWS network ACL imports +an `aws_network_acl` but also one `aws_network_acl_rule` for each rule. In this scenario, the secondary resources will not already exist in configuration, so it is necessary to consult the import output and create