Storage record restriction of gcs paths array causes ingestion to fail
Is now obsolete as the initial approach of adding validation and delete records api was later changed to not rely on this configuration. #178 (closed)
We can safely remove this piece of code.
Due to this, the record creation fails but the response contains the skipped records and no reason is specified its very difficult to know why, someone has to go into the service logs to check it.
Especially if this is invoked from other service during ingestion, tests silently start to fail.
Suggested solution is to either remove this code or add some error message on the API endpoint so it could be relayed to the user.