|
26 | 26 |
|
27 | 27 | A. OPERATION ANALYSIS
|
28 | 28 | - Identify all available operations for the resource
|
29 |
| -- Classify operations by type (create, read, update, delete, list, tag operations) |
| 29 | +- Classify operations by type (create, read, update, delete, tag operations) |
30 | 30 | - Extract ALL input/output fields for each operation (not just shape names)
|
31 | 31 | - Document complete field structures including nested objects
|
32 | 32 | - Determine required vs optional parameters with constraints
|
|
67 | 67 | Create these comprehensive data structures with COMPLETE field analysis:
|
68 | 68 |
|
69 | 69 | # Core Operations Inventory
|
70 |
| -In case there are multiple operations with the same name, choose the one that is most similar to the other operations. Prefer single resource operations over multiple resource operations unless that leads to a mismatch in the field names. |
71 | 70 | operations_catalog = {
|
72 |
| - "create_operations": ["CreateRepository", "PutRepository"], |
73 |
| - "read_operations": ["GetRepository", "DescribeRepository", "DescribeRepositories"], |
74 |
| - "update_operations": ["UpdateRepository", "ModifyRepository"], |
| 71 | + "create_operations": ["CreateRepository"], |
| 72 | + "read_operations": ["GetRepository"], (prefer "Get" over "Describe") |
| 73 | + "update_operations": ["UpdateRepository"], |
75 | 74 | "delete_operations": ["DeleteRepository"],
|
76 |
| - "tag_operations": ["TagResource", "UntagResource", "GetTagsForResource"], |
77 |
| - "other_operations": ["GetRepositoryPolicy", "SetRepositoryPolicy"] |
| 75 | + "tag_operations": ["TagResource", "UntagResource", "GetTagsForResource"] |
78 | 76 | }
|
79 | 77 |
|
80 | 78 | # Field Catalog with Classifications
|
|
220 | 218 | 4. save_error_catalog(error_catalog, service, resource)
|
221 | 219 | 5. save_resource_characteristics(resource_characteristics, service, resource)
|
222 | 220 |
|
223 |
| -5. Report Analysis Summary |
224 |
| -- Operations discovered and classified |
225 |
| -- Field types and characteristics identified |
226 |
| -- Error conditions cataloged |
227 |
| -- Resource behavior patterns noted |
228 |
| -- Data completeness assessment |
| 221 | +5. Report Analysis Summary - Small Summary of the the resource files |
229 | 222 |
|
230 | 223 | Response Format:
|
231 | 224 | 1. "Analyzing AWS {service} {resource} resource..."
|
|
0 commit comments