Ben Kehoe

It could be a new wrapper class with a `__call__` method

You cannot use `ExternalId` with `AssumeRoleWithWebIdentity` ([API docs](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html)). What may suffice is to have your trust policy conditioned on the "sub" claim, as shown here: ```json { "Version": "2008-10-17", "Statement":...

That's a good point, I've changed the title.

@josb what's the use case for that in a CloudFormation template?

Would something that does that operation more directly be a better solution?

Should list-valued identifiers be allowed? We're creating a resource provider for [the sorely-needed S3 bucket notification resource](https://read.acloud.guru/cloudformation-is-an-infrastructure-graph-management-service-and-needs-to-act-more-like-it-fa234e567c82). While the notifications have individual IDs, there is a constraint that no two...

A developer was showing me a template today. They had around 15 template parameters, none of which were intended to be provided by the user of the template. Instead, they...

There's also a problem with the "constants as parameters with default values": changing the default for a parameter in a stack update does not change the value of that parameter,...

I'd say that the value should be able to be *any* valid JSON type, and that putting, say, `Type: Number` on it should allow for conversion of a string containing...

I don't think this should require types that implement list handlers, nor should it need a specification of a property within a resource type. The parameter type should just be...