Bug fixes

• IAM CMDB controls, such as AWS > IAM > Role > CMDB, no longer nest a resource's AWS metadata (account ID, region, partition) inside itself during a mod upgrade. An affected resource lost its account ID and region, so a regional resource's CMDB control looked it up in the wrong region; the CMDB controls now repair the resource in a single run. To find affected resources, filter on $.turbot.custom.aws.aws:!null and run their CMDB control. If that fails with an akas_aka_key error, or the resource stays nested, delete it — discovery keeps or re-creates the correct record.
• The AWS > IAM > Policy > Statements > Approved, AWS > IAM > Group > Inline Policy > Statements > Approved, AWS > IAM > Role > Inline Policy > Statements > Approved and AWS > IAM > User > Inline Policy > Statements > Approved controls no longer sit in tbd for up to an hour on a newly discovered resource. They now wait for the CMDB control and evaluate within seconds of it finishing, instead of running before CMDB has stored the resource.
• These same Statements > Approved controls — AWS > IAM > Policy > Statements > Approved and the versions under AWS > IAM > Role > Inline Policy, AWS > IAM > User > Inline Policy and AWS > IAM > Group > Inline Policy — no longer stay in tbd indefinitely when their Compiled Rules was last calculated while Approved was set to Skip. Such a control now goes to error with a hint to recalculate Compiled Rules, rather than sitting in tbd forever. This release also fixes AWS > IAM > Policy > Statements > Approved > Compiled Rules failing on a policy that has no Terraform stack.