CloudFormation and Cloud Control API actions merged together, no CFN service showing

[eppeters]

Probably due to their sharing an IAM prefix (cloudformation), the actions for Cloud Control API and CloudFormation are both merged under the service name "Cloud Control API" in aws.permissions.cloud.

This could be an issue with the underlying dataset: https://github.com/iann0036/iam-dataset, but I'm not sure.

Note that Cloud Control API actions (e.g. CreateResource) and CloudFormation actions (e.g. CancelUpdateStack) show up on the below page and that no CloudFormation service is listed:

Impact: hard to find CloudFormation actions without using the search functionality and can be confusing.

[iann0036]

Hey @eppeters,

Thanks for catching this one! There's a few services I've seen with this issue.

I've added an override into the dataset which should make it more discoverable, which should be effective when the daily runs in about 8 hours from now.