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
To clarify here according to the spec, what is expected is that since --output is optional and not specified in the above command, we should generate in the ./output folder a sunoWithExtensions-apimanfest.json
The apimanifest.json is currently already generated in the ./kiota folder.
According to the spec, in addition to the already generated apimanifest.json in the ./kiota folder, when choosing --type apimanifest, Kiota should generate a specific apimanifest to the given --open-api named {plugin-name}-apimanifest.json, which in this case is sunoWithExtensions-apimanifest.json in the ./output folder. However, we also need to generate the apimanifest.json in the ./kiota folder.
The apimanifest.json in the ./kiota folder will be a concatenated version of all clients and plugins, that can be used, for example, as a contract with the tenant admin to show all the APIs, endpoints, permissions your solution may need. And one may need a specific apimanifest for the plugin they are creating. A scenario for that is, Semantic Kernel has a under development skill that accepts an API Manifest as input. So one may want to create a specific API Manifest using Kiota to use in SK.
Today, when running Kiota CLI to generate plugins, I can do the following:
However, the output generated is not an API Manifest.
When choosing --type apimanifest, the output file should be an API Manifest.
The text was updated successfully, but these errors were encountered: