node-type of set-community/config/options should be leaf-list

[Taapasee]

When the following node is a leaf-list
/routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-community/reference/config/community-set-refs
The following should also be made a leaf-list, and the count should match in both.
/routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-community/config/options

Similarly for the ext-community.
/routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-ext-community/reference/config/ext-community-set-refs being a leaf-list implies
/routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-ext-community/config/options
should be made a leaf-list with matching count.

[github-actions]

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.

[dplore]

Hi, thanks for the comment.

If multiple options are desired (add, remove, replace) It seems it's possible to have one statement for the add and a separate statement for the delete. This is perhaps a bit more verbose that what you are suggesting.

Do we think we need the complexity of having a list of add,delete,replace to align with a list of community-set-refs? Can you make a concrete use case why this is much better?