Skip to content

!Condition for nested conditions is not handled correctly #99

Description

@amcinnes

I think Stackup transforms !Condition foo into {"Fn::Condition": "foo"} when it should just be {"Condition": "foo"}.

This breaks nested conditions such as the YAML example at the bottom of this AWS doc.

Maybe we need to handle Condition the same way we handle Ref here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions