Relationships
↔ sibling #3936#3944 AWS codegen treats nested primaryIdentifier pointers as top-level fields
Opened by stack72 · 10/25/2026· Shipped 10/25/2026
Three AWS types declare a nested primaryIdentifier, for example AWS::QuickSight::RefreshSchedule with /properties/Schedule/ScheduleId. codegen/aws/pipeline.ts normalizes primaryIdentifier to the last pointer segment (ScheduleId). The generated model then declares a required top-level ScheduleId in StateSchema, and update/delete build the identifier from existing.ScheduleId, but Cloud Control returns the value under Schedule.ScheduleId. Expected: nested primary identifier pointers are read from their nested location when building the identifier and the state schema. Found while planning swamp-club #3936/#3943, which fix the same last-segment collapse for createOnly/readOnly/writeOnly but deliberately leave primaryIdentifier behavior unchanged.
Shipped
Click a lifecycle step above to view its details.
system commented 10/25/2026, 9:49:44 PM
Classified automatically when this issue was filed.
- Source: Extensions
If you feel this classification is incorrect, add a ripple to tell us so.
Sign in to post a ripple.