-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
T5654: policy: move local-route[6] to ip-rule[6] #3781
base: current
Are you sure you want to change the base?
Conversation
👍 |
CI integration 👍 passed! Details
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that this may reduce the confusion. But if we are opening the can of worms and writing a migration script anyway, maybe we should rethink all PBR syntax and see what else we can change?
We may want to change the approach to unify the "local-route" and "route" under a single subtree.
Marking as draft as we need to discuss this internally, in order to analyze if more changes should be included regarding PBR and ip-rules |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
This PR is stale because it has been open 30 days with no activity. The PR will be reviewed by a maintainer and may be closed |
Change Summary
Move
policy [local-route | local-route6]
topolicy [ip-rule | ip-rule6]
Types of changes
Related Task(s)
Related PR(s)
Component(s) name
policy
Proposed changes
How to test
Config valid on 1.3
And after migration
Smoketest result
test_policy.py ==> OK
Checklist: