القائمة
Correct field to use for item descriptions in Read functions — ItemMetadata for DescribeItem, Description for specific Get endpoints. Use when implementing or reviewing d.Set("description", ...) in resource read functions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Guides adding a new Terraform resource or data source end-to-end — SDK update, schema, CRUD, provider registration, tests, and formatting. Use when creating a new resource_*.go or data_source_*.go file, or when the user asks to add a new Terraform resource.
Pattern for Terraform resource import functions — dedicated per-file import func that delegates to Read. Use when adding an Importer to a resource, implementing terraform import support, or reviewing import functions.
Create test fixture dependencies (keys, issuers, targets, secrets) via SDK API calls in test setup, not via Terraform depends_on. Use when writing or reviewing acceptance tests that need pre-existing items, or when a test fails because a Terraform resource references an item that doesn't exist.
Guides updating an existing Terraform resource or data source with new fields or functionality — schema changes, CRUD updates, backward compatibility, and docs regeneration. Use when adding fields to an existing resource_*.go or data_source_*.go file.
| name | item-description-field |
| description | Correct field to use for item descriptions in Read functions — ItemMetadata for DescribeItem, Description for specific Get endpoints. Use when implementing or reviewing d.Set("description", ...) in resource read functions. |
When reading item descriptions in resource Read functions, use the correct field based on the API call.
Use ItemMetadata:
if rOut.ItemMetadata != nil {
err = d.Set("description", *rOut.ItemMetadata)
if err != nil {
return err
}
}
Do not use ItemGeneralInfo.DisplayMetadata.
Use the direct Description field from the response structure.