mirror of
https://github.com/awslabs/iam-policy-autopilot.git
synced 2026-04-26 00:15:57 +03:00
[GH-ISSUE #88] Refactor: Call information should be stored in a single type #152
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/iam-policy-autopilot#152
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mschlaipfer on GitHub (Dec 18, 2025).
Original GitHub issue: https://github.com/awslabs/iam-policy-autopilot/issues/88
We currently store call information in various types, each with small specialization, e.g.,
ChainedWaiterCallInfo,WaitCallInfo, etc. See attached screenshot (which might not be complete):We should refactor this so we avoid code duplication. We could have common and a specialized fields, and we should implement getters on these.
Having separate types led to a lot of duplicated work in https://github.com/awslabs/iam-policy-autopilot/pull/84.
https://github.com/awslabs/iam-policy-autopilot/pull/79 works around it (for Python waiters) by introducing a
CallInfoenum, but this should be removed as part of this refactoring.@mschlaipfer commented on GitHub (Jan 29, 2026):
@adpaco-aws I think this is done?
@adpaco-aws commented on GitHub (Jan 30, 2026):
Partially - #97 didn't remove
CallInfoso I was keeping it open till we do.