You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current version of the exporter allows you to export endpoints from a compiled application (jar or extracted jar). This is mostly useful for integration with tools like ZAP. However, most teams are no longer deploying jar files but docker images instead. In such situations, the current implementation could become hard to use.
Describe the solution you'd like
We're aiming to introduce another version of the exporter, preferably in the same repo (multi module), that allows exporting endpoints from integration tests.
This could be implemented as a junit extension that resolves the current application context and fetches all HandlerMappings:
The HandlerMappings could then be mapped to the OpenAPI format we're currently using. Here a POC.
Pros
you no longer have to build a jar file to export endpoints, potentially reducing build times
easier to use than the standalone version - extending an existing integration test with @ExtendWith(SpringEndpointExporterExtension.class)is all there is to do
Cons
the export is based on the test context, some endpoints might be disabled (e.g. by excluding the controller class from the test context) - it's your responsibility to ensure the export includes all relevant endpoints
The text was updated successfully, but these errors were encountered:
Context
The current version of the exporter allows you to export endpoints from a compiled application (jar or extracted jar). This is mostly useful for integration with tools like ZAP. However, most teams are no longer deploying jar files but docker images instead. In such situations, the current implementation could become hard to use.
Describe the solution you'd like
We're aiming to introduce another version of the exporter, preferably in the same repo (multi module), that allows exporting endpoints from integration tests.
This could be implemented as a junit extension that resolves the current application context and fetches all HandlerMappings:
The HandlerMappings could then be mapped to the OpenAPI format we're currently using. Here a POC.
Pros
@ExtendWith(SpringEndpointExporterExtension.class)
is all there is to doCons
The text was updated successfully, but these errors were encountered: