Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #1

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion 14-Meta-Argument-for_each-Chaining/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ description: Learn Terraform Resource Meta-Argument for_each Chaining
- Because a resource using `for_each` appears as a `map of objects` or `set of strings` when used in expressions elsewhere, you can directly use one resource as the `for_each of another in situations` where there is a `one-to-one relationship` between two sets of objects.
- In our case, we will use the `azurerm_network_interface.myvmnic` resource directly in `azurerm_linux_virtual_machine.mylinuxvm` Resource.

## Step-02: Review Terarform Manifests
## Step-02: Review Terraform Manifests
- Copy the `terraform-manifests` from Section `11-Meta-Argument-count\terraform-manifests-v2` and re-implement this usecase using `for_each`.
- Also apply `for_each` chaining concept
1. c1-versions.tf
Expand Down