All Modules APIs getting deleted upon one Module Import

Hi team, can we please look into this issue. We plan to host multiple of our APIs in one documentation site. We were testing the Module feature as it will allow separation of different schemas and endpoints. We found a dangerous bug which caused a wipe up of all other module’s endpoints.
We basically take imports from our hosted Swagger docs. I set up 3 Modules. All with the setting enabled “delete resources which are not part of the datasource”. My hunch is that instead of it keeping it to the module, it applied this to all other Modules. Since we are mentioning the import to be in a particular module, this setting should apply to the said module and not the entire Project.
Can we please look into it?
I’m on latest version 2.7.26

Thank you for the feedback. We sincerely apologize for the inconvenience this issue has caused you. We will fix this issue immediately.

Thanks Evans. Please do. We need to host multiple APIs and set them to auto import on schedule. This is becoming a blocker. We are using multiple professional licenses in our team and would really appreciate if processes related to Automatic Swagger Imports are working as expected. Thanks again.
Can you please inform me how to best utilize the branch feature? We have set up APIs in main branch and instead of directly taking import into main we would rather take import into maybe stage branch and then do a merge which will give us the visibility on what’s going to affect on the hosted docs. In case of any unexpected change we would be able to fix it on our swagger through code and then take another import into stage. After that merging on main would be safe. Something like that.

Recently we faced a problem where in the new version of Apidog the security schema feature was introduced and it was turned on by default. In the latest import this caused our API headers to show unexpected values which we were not visible prior to that. It was only until our customers reported extra headers when we noticed this. It would have been great if the security schemes features was turned off by default. Issues like this is making us reconsider directly importing into main (hosted docs) branch and first importing into a separate branch then merging to main.

Hello, could you please share the link to your docs site so we can better understand the issue you’re encountering?

If you do not want to import a security scheme for the endpoints, you can click on Advanced Settings on the Scheduled Import Settings page to configure the import settings related to the security scheme.

Have you already manually added security-related headers in the endpoints, and then found duplicate security-related headers due to importing the security scheme?

Yeah I turned that off but until then it was already applied to all 500+ endpoints on our hosted docs. We had to manually go to each endpoint and delete the security headers from there because we handle authentication a different way (through API Gateway) even though our backend (from where OpenAPI swagger gets imported) uses sessionId.
My point was that it would be great features like this be made off by default so problems like this do not occur for ongoing workflows.

Hi, I was testing this in a separate project which is not hosted.

No we intend to turn off security headers for now. However we are facing this issue where even after deleting the security header manually from the endpoint and setting the auth scheme to “Inherit” (the parent folder is set to no Auth) we are seeing a green dot on the Auth tab of endpoints in the hosted docs. One of our team member had also reported this issue in this discord.

Thank you for your feedback. I’ve documented this bug, and we’ll work on fixing it. Please stay tuned for updates.

HamzaJD Thank you for your patience. We have fixed this issue and your endpoints has been restored.

HamzaJD Thank you for your patience. We have fixed the issue where endpoints of other modules were mistakenly deleted after enabling “delete resources which are not part of the datasource.” The endpoints that were mistakenly deleted have also been restored.