data-enrichments-scoped-replace
Use when changing coralogix_data_enrichments update semantics or drift tests. Prefer state-ID delete plus add over partial atomic overwrite for scoped replaces.
67
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/data-enrichments-scoped-replace/SKILL.mdData Enrichments Scoped Replace
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.
- Repository
- coralogix/terraform-provider-coralogix
- Commit
d49bc4c
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.