Using api vrpProvider is considered invalid, it was reverted to default.

[wibisono]

Hi,

I am trying to setup BGP alerter to read vrps from my own routinator instance, with the same config on the docs:

vrpProvider: api
url: http://127.0.0.1:8323/json
preCacheROAs: true

But I am getting the following error:

2023-01-06T13:49:30+00:00 error: The specified vrpProvider is not valid. Using default vrpProvider.

Tracing the error, it looks like api is not recognized as one of the valid providers, when bgp alerter is parsing the RPKI configurations.

Not sure how to patch it, maybe simplest is to recognized it as one possible providers in the rpki-validator helper, or change the logic in parsing this parameter.

Cheers,

[massimocandela]

Hi @wibisono,

I hope all is good with you! Thanks for reporting this, at some point I refactored the validation of the provider parameter and I created this regression. It is now fixed in dev, it will go out with the next release.

[massimocandela]

This is now in the pre-release v1.31.2