Closed Arthurvdv closed 2 years ago
Dear @Arthurvdv ,
Could you supply us the EDMX (via Email if you want to keep it private) of the API thats fails to convert ? That would allow us quicker debug any possible issue.
Kind regards
@AdminHodor, thanks! I've e-mailed you the file(s).
Thanks. We are looking into it. Dear lord ;-). It's a big file 😱.
Not sure if we'll be able to resolve it though ... we're considering our options..
The problem is the size of the file, and the number of paths it's causing. And the library we're using to go from edmx to openapi does not take a depth decently .. so it will produce ALL combinations of paths. Having such a huge API, this is an exploding problem.
I'd recommend to keep the API as small as possible .. that's all I can say for the time being .. we're not sure we'll find a solution, to be honest.. .
We deeply investigated. Since we use an OpenSource library, and the combination with how busines central sets up the multi-level routing .. we come into an endless number of navigation paths. With big APIs (like the default) this is just insane and breaks..
We're going to have to pause this for now.. .
Recommendation: only for custom APIs, only when you have small amount of APIs available in a group.
Thank you for investigating. Unfortunately to hear its not solvable at this moment. Was looking forward to enable this as default on our projects and add this shippable artifact next to the .app file(s).
To be honest it's not a deal breaker at this moment, but it would be awesome to use this feature in the future.
We're not giving up yet - the OpenAPI library has some misteries we need to uncover before we give up ;-)
Dear @Arthurvdv,
The fix was released today in ALOps v1.450. Could you please validate? Downgrading the OpenAPI.OData component from v1.0.9 to v1.0.8 seemed to have done the trick.
Kind regards,
@Arthurvdv - were you able to test this?
I’m currently out-of-the-office. I’l be back beginning of August and make sure to test this again.
Awesome, down to merely 27 seconds!
Describe the bug The idea was to generate the OpenAPI documentation on every pull-request. This PTE with ±60 API pages takes more then 60minutes to run the ALOpsOpenAPI-step isn't workable. Just a wild guess here: Maybe the step is caught in a infinite loop?
The OpenAPI-folder in the artifacts folder on the buildserver is empty.
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior Dependent of the amount of API-objects the time to generate the OpenAPI documentation could vary. My example PTE hasn't extraordinary much API endpoints. I would expect this step to run for a few minutes tops.
Screenshots