Details
-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
0
-
0%
Description
1. Proposed title of this feature request
2. What is the nature and description of the request?
When applying a wrong configuration, e.g.
spec:
desiredState:
routes:
- destination: 200.100.100.0/24
metric: 400
next-hop-address: 11.11.11.254
next-hop-interface: bond0.11
instead of the correct one
desiredState:
routes:
config:
- destination: 200.100.100.0/24
metric: 400
next-hop-address: 11.11.11.254
next-hop-interface: bond0.11
The expectation is the API to instantly rejecte instead of having an error later in the nnce. This is not the case because the desireState
oc explain NodeNetworkConfigurationPolicy.spec.desiredState
KIND: NodeNetworkConfigurationPolicy
VERSION: nmstate.io/v1
DESCRIPTION:
The desired configuration of the policy
3. Why does the customer need this? (List the business requirements here)
A fast feedback will make it clear what is wrong and the user experience will increased.
4. List any affected packages or components.
nmstate operator