Add /validate endpoint to help non-core-platform developers
OSDU application developers working outside of the OSDU core platform do not necessarily have access to OSDU's schema toolchain to ensure that their schemas are correct, consistent with OSDU abstract types, and usable by the indexer.
-
When working with DEVELOPMENT status schema, there is no validation enforced by the schema service in the POST or PUT /schema endpoint. This allows an invalid schema to be installed into OSDU.
-
Subsequently, the storage service PUT /records endpoint will accept data for that (possibly invalid) schema kind without complaint.
-
The application is not aware that the data can't be indexed by the indexer due to invalid schema, and an attempt to reindex data of the invalid schema kind will produce a 500 error from the indexer with no explanation.
If the schema service provided a /validate endpoint that is effectively a dry-run for the POST/PUT /schema endpoint, a lot of uncertainty could be reduced, and lost development time from simple errors could be saved.