Hi team, the new version mentions this feature. However we only utilize our spec for endpoints import and we add our own headers from apidog. Can the team please help that our workflow won’t break in the import (introduce headers coming from spec itself) when we update to this version?
The new feature only affects endpoints with security defined in the OAS. Since I’m not entirely clear about your workflow, you can test this by creating a new project on our web app to see how the update impacts your setup.
We do not intend to include security headers coming from OAS spec. Please share the method to disable it on import. The reason is we use API Gateway and the backend headers are different from API Gateway headers. I hope you understand the use case.
We do not intend to include security headers coming from OAS spec. Please share the method to disable it on import. The reason is we use API Gateway and the backend headers are different from API Gateway headers. I hope you understand the use case.
Could you please share a screenshot of your OAS file and highlight which specific parts you don’t want to import? This will help us better understand your needs.