It should be possible to configure in peers.yaml the list of routers that should be ignored for a specific peer. This would make it easier to not set up a session to a specific peer.
Now you have to configure in peers.yaml to ignore everything that is on PeeringDB and copy the router IPs and prefix limits from PeeringDB to peers.yaml manually. And you have to keep this up-to-date afterwards. This approach will generate issues somewhere in the future.
It should be possible to configure in peers.yaml the list of routers that should be ignored for a specific peer. This would make it easier to not set up a session to a specific peer.
Now you have to configure in peers.yaml to ignore everything that is on PeeringDB and copy the router IPs and prefix limits from PeeringDB to peers.yaml manually. And you have to keep this up-to-date afterwards. This approach will generate issues somewhere in the future.