AWS CloudFormation adds support for Fn:ForEach

My heartburn with the CDK is that it wants to run any such generated CFN, whereas I want it to render any such CFN, the way that troposphere works. Because the quick-create URL that one can give to any potential consumer of the CFN template does not accept CDK code, and "ok, just open a terminal and ..." is the mind-killer for getting other people to deploy something. That's the way GCP thinks about the world and is indescribably painful

If terraform or CDK or tf-cdk work for projects, more power to them, but they are for sure not replacements for each other

Feels like a counter to Terraform for_each.

That depends on ones perspective; it was always possible to use `Transform:` and your own in-Account lambda to do whatever crazy stuff you wanted to the specified structure: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui... ( and its friend https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui... ); two of the existing ones were AWS::Include and AWS::Serverless

however, that placed the burden upon the user to (a) ensure said lambdas were deployed, in every account, and (b) that the lambda worked reliably for all possible inputs

It'd be like if python started shipping with a binding to jq: great for the places where it's available, but otherwise you need to have a strategy for when it's not. Now, the "cloudformation standard library" includes it OOtB which can help things like Fn::ForEach::TheAZs: [ "MyAZ", { Ref: Fn::GetAZs }, ... ] which previously was monster stupid to work around