A new schema attribute needs a matching attr.Type map entry
SkillCloud & infraUse when a coralogix_dashboard apply or state upgrade fails with 'Value Conversion Error' at 'Path: layout' after adding a widget attribute. Widen the hand-written attr.Type map too.
Use A new schema attribute needs a matching attr.Type map entry in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add A new schema attribute needs a matching attr.Type map entry and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the A new schema attribute needs a matching attr.Type map entry skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by coralogix/terraform-provider-coralogix in .claude/skills/schema-attribute-needs-matching-attr-type-map/SKILL.md and read by Ahel’s review.
Trigger: You added an attribute to a widget schema. The build passes, but tests or applies
fail with Value Conversion Error and Path: layout, listing two near-identical type dumps.
Fix: Widen every hand-written map[string]attr.Type that describes the same object, not just
the schema. For dashboards that is widgetModelAttr() in
internal/provider/dashboards/resource_coralogix_dashboard.go:
"color_scheme": types.StringType,
"hash_colors": types.BoolType, // add next to the neighbours you copied in the schema
Grep both sides before you start; a widget may be described in more than one place:
rg '"<new_attribute>"' internal/provider/dashboards # schema sites
rg '"<sibling_attribute>": types\.' internal/provider/dashboards # attr.Type map sites
To find the mismatch fast, diff the two type dumps from the error rather than reading them.
Faster: go test ./internal/provider/dashboards/ -run TestWidgetSchemaMatchesWidgetModelAttr
walks the whole widget tree and names the attribute that is in one side and not the other.
Why: layout is a types.List of widget objects. The framework builds the element type from
the attr.Type map and the state type from the schema. It rejects any object whose two descriptions
differ, even by one attribute. Whether the Go model field is a struct pointer or a types.Object
does not matter — what matters is that some ancestor is a list or object described by a hand-written
map, which is true of every dashboard widget.
Signals
- GitHub stars
- 22
- Forks
- 14
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
schema-attribute-needs-matching-attr-type-map- Source
- github.com/coralogix/terraform-provider-coralogix
github.com/coralogix/terraform-provider-coralogix
Related picks
Skill · samber
The pick for Gogo-sdk-specialist
Skill · a5c-ai
The pick for Govercel-react-best-practices
Skill · vercel-labs
More in Cloud & infraweb-design-guidelines
Skill · vercel-labs
More in Cloud & infraturborepo
Skill · vercel
More in Cloud & inframicrosoft-foundry
Skill · microsoft
More in Cloud & infra