Skip to content

Commit 1c31291

Browse files
authored
fix: indentation
1 parent 781968a commit 1c31291

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

src/content/docs/infrastructure-as-code/terraform/migrate-drop-rules-to-pipeline-cloud-rules.mdx

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -54,14 +54,14 @@ This section describes the standard Terraform workflow for migrating from `newre
5454
Navigate to your Terraform working directory and run one of the following commands:
5555

5656
```bash
57-
# Apply to update state with pipeline_cloud_rule_entity_id
58-
terraform apply
57+
# Apply to update state with pipeline_cloud_rule_entity_id
58+
terraform apply
5959

60-
# Safer: use refresh-only to see changes without modifying infrastructure
61-
terraform apply -refresh-only
60+
# Safer: use refresh-only to see changes without modifying infrastructure
61+
terraform apply -refresh-only
6262

63-
# Targeted: limit operation to specific drop rule resources
64-
terraform apply -refresh-only -target=newrelic_nrql_drop_rule.foo
63+
# Targeted: limit operation to specific drop rule resources
64+
terraform apply -refresh-only -target=newrelic_nrql_drop_rule.foo
6565
```
6666

6767
After running one of the above commands, the `pipeline_cloud_rule_entity_id` will be available in your state for each drop rule. Keep the IDs handy for the next step.
@@ -620,7 +620,8 @@ To simplify the native Terraform migration workflow described above, New Relic p
620620
action = "drop"
621621
nrql = "SELECT * FROM Log WHERE contains(message, 'SSN')"
622622
}
623-
``` */}
623+
```
624+
*/}
624625
</Step>
625626

626627
<Step>

0 commit comments

Comments
 (0)