Steve Bjorg
Steve Bjorg
I would recommend the function contains an action verb as well, such as `Fn::MakeArn`. When I first read the issue title, I thought this was going to fix the pain...
I know I'm too late to the party, but disguising functionality that is introduced by transforms as native CloudFormation intrinsic is confusing. This shouldn't have had just the `Fn::` prefix....
This is hugely beneficial. Big +1! When can we get this? The `Value` key should support 3 types of notation: string, list, and map. Also, `Type` should be optional. ```yaml...
As far as I can tell, the only literal type in CloudFormation is `string`. The various parameter types, such as `Number` are just input validators (as well as transforms, but...
How is this a language feature? This is a CLI issue, no?
@Ponsdurai That doesn't solve the issue though.
Agree that map is the way to go over loops. You should be able to prototype this as a transform, correct? That way, you could validate the notation on concrete...
Alternatively, a version of `AWS::Include` that allows loading of plain text and feeding it to `Fn::Sub`. Something like: ``` !Sub - !IncludeText s3://my-bucket/my-stages.yaml - SourceS3Bucket: !Ref MyBucket SourceS3ObjectKey: "my-key" ApplicationName:...
Allowing expressions directly in the `Condition` property and having #55 would probably address the original concern, no?
I just want to heed caution on AWS Kinesis. Unlike the other services, Kinesis semantics are quite different. It's a stream, which means, no next records can be read until...