ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Sathija Pavuluri 2020-04-07 20:36:02 -04:00 committed by GitHub
parent 2eba39a671
commit a0832b9886
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/docs/import/usage.html.md
View File

@ -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 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 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 multiple resources are imported. For example, an AWS network ACL imports
an `aws_security_group` but also one `aws_security_group_rule` for each rule. 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 In this scenario, the secondary resources will not already exist in
configuration, so it is necessary to consult the import output and create configuration, so it is necessary to consult the import output and create