ClusterLabs
Route: Allow specifying a routing metric value
The Route resource did not previously support setting a routing metric (i.e. a priority which the newly created route will carry). This is a common requirement, and is already supported in agents such as IPsrcaddr and IPaddr2.
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/resource-agents/job/resource-agents-pipeline/job/PR-2051/1/input
![knet-jenkins[bot] avatar](https://avatars.githubusercontent.com/u/32407685?v=4 "Published by a pub.dev verified publisher"){kind=small}
LGTM. I'll leave this open for a week or 2 for others to review and test it.
Apologies, have just spotted a bug. I'll revise. (correction: I will force-push later today when I have access to my hardware key).
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/resource-agents/job/resource-agents-pipeline/job/PR-2051/3/input