Skip to content
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.

Allow unknown fields on AWS::CloudFormation::CustomResource #193

Closed
jarreds opened this issue Mar 22, 2019 · 2 comments
Closed

Allow unknown fields on AWS::CloudFormation::CustomResource #193

jarreds opened this issue Mar 22, 2019 · 2 comments
Labels
bug

Comments

@jarreds
Copy link
Contributor

jarreds commented Mar 22, 2019

Dynamic fields are par for the course in AWS::CloudFormation::CustomResource.
@PaulMaddox PaulMaddox added the bug label Mar 27, 2019
@toddobryan-clever
Copy link

It would also be nice if there were a way to use the Custom::String type instead of AWS::CloudFormation::CustomResource. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cfn-customresource.html#aws-cfn-resource-type-name

I've included this here since I think these two could probably be fixed in one code block, but I'm happy to create another ticket if that would help.

@mweagle
Copy link

mweagle commented Apr 23, 2019

I would also like to see support for custom fields and Custom::String .

@mweagle mweagle mentioned this issue Apr 27, 2019
Open
@grahamjenson grahamjenson mentioned this issue Jun 18, 2019
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mweagle @jarreds @PaulMaddox @toddobryan-clever