When using a OAS 2.0 (maybe 3.0) JSON Specification as the "mainRamlFile" in mule-deploy, the pipeline succeeds without errors. However, when opening the the deployed project in exchange the following error from mulesoft is provided "Error loading API: Error.captureStackTrace is not a function" as well as similar javascript errors causing the documentation to fail to load. See screenshot attached. However, when I manually deploy the design center project to exchange it works fine, so I believe it has to do with the mule-deploy and not the file itself. I have tried this with replication on a few design center projects now.
When using a OAS 2.0 (maybe 3.0) JSON Specification as the "mainRamlFile" in mule-deploy, the pipeline succeeds without errors. However, when opening the the deployed project in exchange the following error from mulesoft is provided "Error loading API: Error.captureStackTrace is not a function" as well as similar javascript errors causing the documentation to fail to load. See screenshot attached. However, when I manually deploy the design center project to exchange it works fine, so I believe it has to do with the mule-deploy and not the file itself. I have tried this with replication on a few design center projects now.