[GH-ISSUE #110] Distinguish a waiter from a "regular" SDK call #94

New issue

Open

opened 2026-03-07 19:41:54 +03:00 by kerem · 0 comments

kerem commented

2026-03-07 19:41:54 +03:00

Owner

Originally created by @mschlaipfer on GitHub (Jan 20, 2026).
Original GitHub issue: https://github.com/awslabs/iam-policy-autopilot/issues/110

See https://github.com/awslabs/iam-policy-autopilot/pull/109/files/2edcb2ad06d5bedfafab7754006793eb833434d5#r2709693207.

When creating a waiter we currently need to map the waiter to the operation during extraction. This is because

We need the operation name to avoid the SdkMethodCall being filtered out during disambiguation.
Enrichment (and the SdkMethodCall type) currently does not perform waiter to operation resolution, which means that a custom extractor (or agent or human user) needs to know how to map a waiter to its operation.

We should introduce a way to distinguish a waiter from a "regular" SDK call and store the waiter name here. We should add support for resolving the waiter -> operation map during enrichment.

Originally created by @mschlaipfer on GitHub (Jan 20, 2026). Original GitHub issue: https://github.com/awslabs/iam-policy-autopilot/issues/110 See https://github.com/awslabs/iam-policy-autopilot/pull/109/files/2edcb2ad06d5bedfafab7754006793eb833434d5#r2709693207. When creating a waiter we currently need to map the waiter to the operation during extraction. This is because 1) We need the operation name to avoid the `SdkMethodCall` being filtered out during disambiguation. 2) Enrichment (and the `SdkMethodCall` type) currently does not perform waiter to operation resolution, which means that a custom extractor (or agent or human user) needs to know how to map a waiter to its operation. We should introduce a way to distinguish a waiter from a "regular" SDK call and store the waiter name here. We should add support for resolving the waiter -> operation map during enrichment.