We need to adapt the gbfs-validator-pubsub function functions-python/gbfs_validator to the new gbfs-validator-java.
Currently the gbfs-validator-pubsub function makes calls to the original gbfs-validator deployed on netlify.
The URL used for the call is here
Here is an example of a validation report as return form the aPI call:
Bixi validation report
With MobilityData/gbfs-validator-java-infra#3 we will have the new gbfs-validator-java API deployed. The API is slightly different (See openapi.yaml). As an example, this call:
curl -X 'POST' \
'http://localhost:8080/validate' \
-H 'accept: application/json' \
-H 'Content-Type: application/json' \
-d '{"feedUrl": "https://cluster-prod.veoride.com/api/shares/name/wta/gbfs"}
(You need to have started the API locally). Here is the return:
{
"summary": {
"validatorVersion": "2.0.68",
"files": [
{
"name": "gbfs",
"url": "https://cluster-prod.veoride.com/api/shares/name/wta/gbfs",
"version": "2.2",
"language": null,
"errors": [],
"schema": "The json schema for the GBFS auto-discovery file"
"systemErrors": []
},
{
"name": "system_information",
"url": "https://cluster-prod.veoride.com/api/shares/name/wta/gbfs/system_information",
"version": "2.2",
"language": "en",
"errors": [],
"schema": "The json schema for the GBFS system_information file",
"systemErrors": []
},
...
]
}
}
We need to adapt the gbfs-validator-pubsub function functions-python/gbfs_validator to the new gbfs-validator-java.
Currently the gbfs-validator-pubsub function makes calls to the original gbfs-validator deployed on netlify.
The URL used for the call is here
Here is an example of a validation report as return form the aPI call:
Bixi validation report
With MobilityData/gbfs-validator-java-infra#3 we will have the new gbfs-validator-java API deployed. The API is slightly different (See openapi.yaml). As an example, this call:
(You need to have started the API locally). Here is the return: