About versions modules

[hsineternity]

Why is there no Version included in the Module ID? In the /details API, the ModuleID is set to 'credentials.' Does this indicate that the Version module may not be required or has not been implemented?

Regarding the Version module, I have the following questions:

1. Within the version API, it seems that the content for /versions and /details is hardcoded in the project. Is there a way to make this content more flexible or customizable?

2. In /ocpi/versions, it appears that it doesn't enter the Crud class. How can we verify the correctness of the Authorization Token in this case? According to OCPI spec 2.2.1, specifically in the seventh chapter (Figure 22 - "The OCPI registration process"), /ocpi/versions should carry the token within the header.

[VictorTechs]

Hi @hsineternity, sorry for the very long response, if you are able to create a fix, we will review it and merge it.

[IOR88]

Hi @hsineternity we are now getting back to ocpi library maintenance, we will soon take care of the request you created, have you successfully integrated ocpi lib with your project ?