Large Enough Stacks Will Probably Start To Have Span Data Missing

[Grunet]

This is coming from the code not currently handling pagination of the AWS JS SDK calls at all (it's just making one call and calling that good).

This AWS doc about when pagination starts suggests its around when the response gets to 1 MB. When I measured the hollow-nesting-only (root) stack it came out to about 4000 bytes per deploy, which implies that it's roughly when a stack is 250 times as big (so like 250 resources) when problems would start to appear

[Grunet]

I think the code changes for this are straightforward, just actually making a large enough stack to end-to-end test it felt a little daunting when I thought about this before

[Grunet]

It seems like Cloudformation has a limit of 500 resources per stack? Per this - https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-limits.html