Kapil Thangavelu

If your explicitly specifying run a region in the accounts config file for a given account, stopping due to error is the correct thing for us to do as it’s...

fwiw, cloudcustodian.io supports asgs, rds, redshift, ec2 etc for off hours functionality for several years, if folks want something opensource, actively developed, well tested, with these features today.

I'd prefer a tree shape to be able to understand the top level depend, ie which package in a workspace pulled in this dependency.

cloud custodian is a cloud management tool, it does require understanding the underlying cloud infrastructure thats being managed. there are numerous examples for ingress filters in the documentation https://cloudcustodian.io/docs/aws/resources/security-group.html#aws-security-group-filters-ingress but...

so i think there was a bit of mismatch on expectation here that multiple filters would narrow down the same set, and they do on resources, but the filter was...

> With Cloud Custodian though, the key evaluation won't allow for the JMES query and the former does not return anything though per the documentation I believe it should. so...

curiosity what's the goal/use case in supporting Moto in this context?

there's a class attribute for annotationing matched items that currently defaults to false in the base class.

fwiw, it looks like its failing coverage checks, because none of the recorders in the tests have a retention configuration set.

fwiw, I'm simplifying this to use value filter builtin keywords `value: empty` and `value: present` which removes some of the conditional logic, and testing.