[aws-ec2] Isn't IVpc supposed to be implemented by users?

[foriequal0]

Current IVpc has both properties and methods. These methods are implemented in VpcBase, and they are reused throughout the aws-cdk codebases.
I've built my MyVpc construct with L1 constructs from scratch to match my requirements. (#5927 (comment)) As I've commented, they don't play well with existing L2 constructs.
In order to plug my MyVpc into other L2 constructs, I have to re-implement methods that are already implemented in VpcBase. It is tedious and worrisome.
I'm getting an impression that IVpc isn't supposed to be implemented by users.

Use Case

Proposed Solution

To lower the barrier of implementing IVpc, we should improve the reusability of methods that are implemented in VpcBase.

1. Separate IVpcProps from IVpc to only contain properties.
2. Refactor methods in VpcBase to only depend on IVpcProps, not this IVpc.
3. Replace IVpc method usages with the methods that are refactored in 2.

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[rix0rrr]

Are there specific reasons you cannot inherit from VpcBase?

[foriequal0]

@rix0rrr It is not exported...

[rix0rrr]

Oh I see.

Well yeah, this needs consideration in the VPC redesign, so good call on linking that in. I'm not sure there's something we can do at short notice without committing to an API we won't want to maintain in the future.

I'd recommend copy/pasting the class for now. Sorry I don't really have a better answer for you.

[github-actions]

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.