Right now there is a rather arbitrary MUST NOT exceed max 2MB file size constraint for adding resource definitions.
In practice we've seen that there are bigger documentas around, allthough they sometimes cause problems (e.g. big OpenAPI files crash SwaggerUI Renderer). However, it's hard to put an arbitrary file size limit on it and it's also not easily possible to split up or trim down metadata files when they exceed the size.
So we should probably change this into a RECOMMEND statement. We may want to have a hard limit, too - but I wonder if this should rather be enforced by the ORD Aggregator, as this could also depend on its limitation and scalability.
Right now there is a rather arbitrary MUST NOT exceed max 2MB file size constraint for adding resource definitions.
In practice we've seen that there are bigger documentas around, allthough they sometimes cause problems (e.g. big OpenAPI files crash SwaggerUI Renderer). However, it's hard to put an arbitrary file size limit on it and it's also not easily possible to split up or trim down metadata files when they exceed the size.
So we should probably change this into a RECOMMEND statement. We may want to have a hard limit, too - but I wonder if this should rather be enforced by the ORD Aggregator, as this could also depend on its limitation and scalability.