Update Cloudwatch client to ensure limits in query

[zachmargolis]

Why: Without a "| limit 10000", the script will not be able to detect missing data, so it won't return the expected results

[aduth]

Would it make sense to include this automatically?

[zachmargolis]

Would it make sense to include this automatically?

I'm not sure if we can safely append that in 100% of queries, I'm not sure if clause order matters

[aduth]

👍

[rebecca-e-wright]

Is there any type of check that could also be put in that would make sure the "--complete" flag was also present? Not sure if thats an option since it's part of the script parameters and not the embedded cloudwatch query.

[zachmargolis]

Is there any type of check that could also be put in that would make sure the "--complete" flag was also present? Not sure if thats an option since it's part of the script parameters and not the embedded cloudwatch query.

--complete is an optional flag, making it default to on seems a little trickier since not all queries are intended to have it?

[zachmargolis]

Would it make sense to include this automatically?

I'm not sure if we can safely append that in 100% of queries, I'm not sure if clause order matters

Following up after doing some more research for #10875, I think that anything with | stats or | dedup are also ones we can't reason about with this logic, so I do think it's good to throw an error and have a human double check the query strategy