菜单
Use when changing coralogix_data_enrichments update semantics or drift tests. Prefer state-ID delete plus add over partial atomic overwrite for scoped replaces.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a Terraform Plugin Framework resource import reads required DynamicAttribute values. Handle imported partial state before converting dynamic values.
Use when creating a PR for a non-trivial bug fix in this repo. Assembles a structured PR description following .github/PULL_REQUEST_TEMPLATE.md with expanded sections for root cause, risks, and test plan. Do NOT use for trivial one-liner fixes.
Use when validating a Coralogix terraform-provider bug fix end-to-end against a real Coralogix environment. Builds the provider locally, runs multi-step Terraform apply/plan scenarios to verify idempotency, and catches perpetual-diff regressions before merge.
| name | data-enrichments-scoped-replace |
| description | Use when changing coralogix_data_enrichments update semantics or drift tests. Prefer state-ID delete plus add over partial atomic overwrite for scoped replaces. |
Trigger: updating internal/provider/enrichment_rules/resource_coralogix_data_enrichments.go or debugging duplicated geo_ip, suspicious_ip, aws, or custom fields after update.
Fix: For resource-scoped updates, read prior state IDs, call EnrichmentServiceRemoveEnrichments for only those IDs, then call EnrichmentServiceAddEnrichments with the planned fields. Do not use EnrichmentServiceAtomicOverwriteEnrichments for mixed non-custom resources.
Why: The partial atomic-overwrite API is typed and can append planned enrichments beside existing ones when Terraform manages multiple enrichment types, producing inconsistent-result errors and duplicated backend state.
