Command-base integration with Kiota should support .kiota folder

[maisarissi]

As part of the command-base integration between Kiota and TTK, .kiota folder should be supported. .kiota folder includes the following:

• workspace.json file, which is Kiota's input files used to generate clients and plugins. So, supporting this in the integration is vital to help one maintaining their clients/plugins.
• apimanifest.json file, which represents a snapshot and a concatenated surface of all APIs used across plugins and clients. Both files, apimanifest.json and workspace.json will be used to generate the code files. A new hash composed of the Kiota version, the OpenAPI document location and the properties of the manifest will be generated and would trigger an update to the API Manifest in case there is any change.
• documents folder, which contains a copy of all OpenAPI descriptions used to generate clients/plugins

As previous discussed with TTK team, supporting users in editing existing plugins, is one of their current goals and Kiota can provide that.

So when calling fx-extension.createprojectfromkiota, .kiota folder path should be one of the parameters. With that, once the first generation is done, through the integration, one will be able to edit existing plugins from Kiota extension.

Open questions:

• Once .kiota is supported, what would be the best way to handle adaptive cards re-generation?
  • Kiota adding adaptive cards generation and every time one's re-generate their plugin always replace the current adaptive cards based on the endpoints selection would be the best way moving forward? Benefit is always to add the new endpoints as part of the adaptive cards. Drawback: Override users custom edits.
  • Use a different file only for adaptive cards and TTK can include its content when provisioning? Benefit is to not override custom changes based on user's changes. Drawback: All additions after the first generation would need to be added manually.
• After regenerating, Kiota updates relevant files (API plugin, API manifest, sliced OpenAPI description and might update the copy of the OpenAPI in the documents folder). Should Kiota just call the fx-extension.createprojectfromkiota with the new re-generate content or there will be a new command just to the regeneration?

[microsoft-github-policy-service[bot]]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.