Closed robertstettner closed 4 years ago
Hmm... so I don't doubt that this is true, and a valid bug. However it's also likely never going to impact us here at Manheim, for various reasons (including that we run c7n in a minimum set of regions in every account, regardless of whether the regions are actually "in use" in that account or not).
I can't make any promises about when this will get fixed. I'll do my best to address it next time I do some major work on this project. Aside from that, pull requests are always welcome.
This has been released in 0.8.5, which should be published shortly. Thanks so much for reporting it!
The tool complains that the
us-east-1
region is required. Furthermore, after adding it in the config, if there are no account-wide, or org-wide policies, and only certain region policies, barring theus-east-1
, because say, we don't use that region, what shall we do?The error for when the tool tries to run no policies for a region is below:
The error for the tool complaining it needs the
us-east-1
region is: