Skip to content

[design]: Remove need to use legacy and private decorators in Network spec #4435

Description

@markcowl

To prevent a name clash with a custom ProxyResource, network specs cannot use standard resource templates for new resources. We should create a mechanism where private dcorators and suppressions are not needed for new ntwork resources. This could be:

Metadata

Metadata

Assignees

Labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions