As a developer, I want to have a sliced OpenAPI document with only the endpoints and components used by my solution when generating a plugin

[maisarissi]

Is your feature request related to a problem? Please describe the problem.

Kiota produces large OpenAPI documents even when only one endpoint is selected because it doesn’t remove unused components.

Client library/SDK language

None

Describe the solution you'd like

When generating plugin and clients, Kiota should be able to trim unused components from the original OpenAPI document to generate a clean sliced OpenAPI document with only the information that is important for my solution.

For clients:

• Remove all unused components and keep all used components including schemas, parameters, responses.
• Remove all extensions (starts with x-) that don't match with our internal documentation of supported extensions in Kiota.

For plugins:

• Removes all unused components and keep only schemas and parameter of used components. For plugins we should also remove any responses components as this won't be used by orchestrators and can increase the size of the OpenAPI document.
• Remove all extensions (starts with x-) that don't match with our internal documentation of supported extensions in Kiota.

Additional context

No response

[andrueastman]

Just to confirm here, @maisarissi
Is the desired openApi document the document the document in the .kiota folder (especially for client generation)?
Does this mean that for plugin generation, the document in the plugin output folder should now match the one in the .kiota folder?

[andrueastman]

Limiting the scope of the issue to plugin generation that has an output yaml that will be trimmed via generation at #4748

With regards to client generation, open questions above with regards to handling of .kiota folder documents will be addressed via client generation issue at #4770