tfgen-set-of-objects-and-go-names
Use when tfgen check fails with RENDERER_SHAPE_UNSUPPORTED set of object, or RENDERER_OUTPUT_INVALID on a dotted OpenAPI component like notification_center.ConnectorConfigField. Fix collectionConv and modelTypeName, not the generated files.
72
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
tfgen sets of objects and namespaced components
Trigger: tfgen check reports set of object is not supported, or generated model.go has an invalid type such as notification_center.FooModel.
Fix:
- Sets of objects:
collectionConvmust acceptmodel.Setof objects (empty objects still rejected). Expand/flatten useexpandElementsandflattenSet; nested diagnostics use the collection path, notAtListIndex. Do not pair set items with prior by slice index. NestedkeepPriorOrderlists still usesameUnorderedinsame*. The Thing golden fixture must include a set of objects so this flatten path is generated. - Namespaced components:
modelTypeNamemust bemodel.GoName(schema)+"Model", same as SDKcamelize. Do not concatenate the raw schema name.
Why: OpenAPI x-coralogix-collection: set on object arrays is the contract for Terraform Sets. Dotted component names are valid OpenAPI keys but not Go identifiers.
- Repository
coralogix/terraform-provider-coralogix
- Revision
8110e9e
- 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.