Skip to content
Merged
Changes from 1 commit
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
Prev Previous commit
Next Next commit
fix: indentation
  • Loading branch information
brnhensley authored Dec 3, 2025
commit 1c312915299b59a62b0e18172dba867c346a425c
Original file line number Diff line number Diff line change
Expand Up @@ -54,14 +54,14 @@ This section describes the standard Terraform workflow for migrating from `newre
Navigate to your Terraform working directory and run one of the following commands:

```bash
# Apply to update state with pipeline_cloud_rule_entity_id
terraform apply
# Apply to update state with pipeline_cloud_rule_entity_id
terraform apply

# Safer: use refresh-only to see changes without modifying infrastructure
terraform apply -refresh-only
# Safer: use refresh-only to see changes without modifying infrastructure
terraform apply -refresh-only

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

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.
Expand Down Expand Up @@ -620,7 +620,8 @@ To simplify the native Terraform migration workflow described above, New Relic p
action = "drop"
nrql = "SELECT * FROM Log WHERE contains(message, 'SSN')"
}
``` */}
```
*/}
</Step>

<Step>
Expand Down
Loading