(1) /routing-policy/policy-definitions/policy-definition/statements/statement/conditions/match-interface/config/:
As per the current schema, only one match-interface can be specified for a given statement. Should there be a provision to add a list of interfaces?
2) /routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-community/reference/config/community-set-ref:
As per the current schema, only one community-set can be referenced in a given action. Should this be made a leaf-list?
(3) /routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-ext-community/reference/config/ext-community-set-ref:
As per the current schema, only one ext-community-set can be referenced in a given action. Should this be made a leaf-list?
This issue is stale because it has been open 180 days with no activity. If you wish to keep this issue active, please remove the stale label or add a comment, otherwise will be closed in 14 days.
(1) /routing-policy/policy-definitions/policy-definition/statements/statement/conditions/match-interface/config/: As per the current schema, only one match-interface can be specified for a given statement. Should there be a provision to add a list of interfaces?
2) /routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-community/reference/config/community-set-ref: As per the current schema, only one community-set can be referenced in a given action. Should this be made a leaf-list?
(3) /routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-ext-community/reference/config/ext-community-set-ref: As per the current schema, only one ext-community-set can be referenced in a given action. Should this be made a leaf-list?