Skip to content

Conversation

@tejaswaroop-nr
Copy link
Contributor

Migration docs for Pipeline cloud rules with Terraform

@tejaswaroop-nr tejaswaroop-nr self-assigned this Oct 6, 2025
@tejaswaroop-nr tejaswaroop-nr added content requests related to docs site content from_tw Identifies issues/PRs from Tech Docs writers labels Oct 6, 2025
@github-actions
Copy link

github-actions bot commented Oct 6, 2025

Hi @tejaswaroop-nr 👋

Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local.

If you really require a preview url, reach out to one of the writers and they will generate one for you.

@tejaswaroop-nr
Copy link
Contributor Author

Netlify build

@github-actions
Copy link

github-actions bot commented Oct 9, 2025

🚀 Netlify Preview Building!

If the build is successful, the preview for this pull request will be available at the following URL (usually takes 10-20 minutes):

https://pipeline-cloud-rules-migration--docs-website-netlify.netlify.app

@tejaswaroop-nr
Copy link
Contributor Author

Netlify build

@tejaswaroop-nr
Copy link
Contributor Author

@tejaswaroop-nr
Copy link
Contributor Author

Netlify build

@tejaswaroop-nr
Copy link
Contributor Author

Netlify build

@tejaswaroop-nr
Copy link
Contributor Author

@tejaswaroop-nr
Copy link
Contributor Author

Netlify build

@tejaswaroop-nr
Copy link
Contributor Author

Netlify build

Comment on lines 898 to 922
{/* The following content will go into a troubleshooting guide

## Troubleshooting [#troubleshooting]

### Import fails with "resource not found"

If imports fail during `terraform apply`:

**Solution:** Run `terraform refresh` to ensure your state is synchronized with New Relic, then verify the `pipeline_cloud_rule_entity_id` values are correct in your state file (for local approach) or JSON file (for GitOps approach).

### Plan shows unexpected changes after migration

If `terraform plan` shows changes after successful migration:

**Solution:** This usually indicates the generated `pcrs.tf` doesn't match the actual resource configuration. Review and adjust the generated configuration to match your New Relic settings exactly.

### Old drop rules still showing in Terraform state

If `terraform state list` still shows `newrelic_nrql_drop_rule` resources after migration:

**Solution:** Use the `terraform state rm` command to manually remove them from state without deleting them from New Relic. For example:
```bash
terraform state rm newrelic_nrql_drop_rule.rule_name
```
Follow the recommendations provided in the CLI output from Phase 2 for the complete list of resources to remove. */}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content requests related to docs site content from_tw Identifies issues/PRs from Tech Docs writers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants