Skip to content

Investigate ways to reuse code between MultiCidrVpc and MultiTierVpc #234

Description

@ryanjjung

These two classes have a lot in common because the latter was clone from the former. Going forward, any bugs fixed or features added will likely require updates to both classes. This should be unnecessary, and it's kind of an anti-pattern. Let's figure out what this looks like (even if this looks like deprecating MultiCidrVpc, as I suspect it might).

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    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