-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Drop rules to Pipeline cloud rules #21857
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
base: develop
Are you sure you want to change the base?
Conversation
|
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. |
|
Netlify build |
🚀 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 |
|
Netlify build |
|
Netlify build |
|
Netlify build |
|
Netlify build |
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
|
Netlify build |
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Show resolved
Hide resolved
| {/* 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. */} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tejaswaroop-nr this sounds like a comment you've added, so this can be added to a different guide in future; I don't think we need to document this for inclusion somewhere else, as I would suggest adding a "References" section that would lead to
- https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/guides/drop_rules_eol_guide#nrql-drop-rules-eol-implications-and-actions-needed
- https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/pipeline_cloud_rule
- https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/nrql_drop_rule
- https://github.com/newrelic/terraform-provider-newrelic/tree/main/examples/drop_rule_migration_ci#troubleshooting
- https://github.com/newrelic/newrelic-cli/blob/main/internal/migrate/tf_importgen_ci_guide.md
- https://github.com/newrelic/newrelic-cli/blob/main/internal/migrate/tf_importgen_guide.md
with each of these shown with relevant labels such as Troubleshooting for the CI workflow, Troubleshooting for the local workflow, etc - do you think this would make sense
src/content/docs/data-apis/manage-data/migrate-drop-rules-to-pipeline-cloud-rules.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Pranav Nandula <[email protected]>
Migration docs for Pipeline cloud rules with Terraform