You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the context of KonnectID references, the KonnectGatewayControlPlane has to be improved to belong to different types: origin and mirror.
Proposed Solution
Add a new type field to the KonnectGatewayControlPlane spec. This field is an enum that can have two possible values:
origin (default enforced by cel)
mirror
Together with the type field, a new MirrorSpec field has to be added: this field is a struct that contains (for the time being) only a string for the konnectID.
Cel validation is added to ensure that:
in case type is origin, MirrorSpec is empty
in case type is mirror, MirrorSpec is not empty and the origin-related fields (the ControlPlane spec) are empty
Acceptance Criteria
As a user, I can set a KonnectGatewayControlPlane to be either of origin type or mirror type.
The text was updated successfully, but these errors were encountered:
Problem Statement
In the context of
KonnectID
references, theKonnectGatewayControlPlane
has to be improved to belong to different types:origin
andmirror
.Proposed Solution
Add a new
type
field to theKonnectGatewayControlPlane
spec. This field is an enum that can have two possible values:origin
(default enforced by cel)mirror
Together with the type field, a new
MirrorSpec
field has to be added: this field is a struct that contains (for the time being) only a string for thekonnectID
.Cel validation is added to ensure that:
MirrorSpec
is emptymirror
,MirrorSpec
is not empty and theorigin
-related fields (the ControlPlane spec) are emptyAcceptance Criteria
KonnectGatewayControlPlane
to be either oforigin
type ormirror
type.The text was updated successfully, but these errors were encountered: