Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When regenerating a plugin, TTK is not updating the DAs conversation starters #13127

Open
maisarissi opened this issue Feb 5, 2025 · 1 comment
Labels
needs attention This issue needs the attention of a contributor.

Comments

@maisarissi
Copy link

When generating first time a DAs with plugin using TTK + Kiota, everything works as expected.

When regenerating the plugin (add/remove endpoints), everything gets updated but DAs conversation starters.

TTK should also update the conversation starters based on the updated plugin info.

Copy link

👋 Hi @maisarissi,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

It sounds like you are encountering an issue where the Teams Toolkit (TTK) is not updating the Digital Assistants (DAs) conversation starters when regenerating a plugin using Kiota. This is a known issue and has been discussed in a GitHub issue.

Problem

When regenerating a plugin and making changes such as adding or removing endpoints, everything gets updated except for the DAs conversation starters. This can lead to inconsistencies and outdated information in the DAs.

Proposed Solution

The solution involves ensuring that the Teams Toolkit updates the conversation starters based on the updated plugin information when regenerating the plugin. Here are some actionable steps to resolve this issue:

  1. Include .kiota Folder Path:
    Make sure to include the path to the .kiota folder when calling the fx-extension.createprojectfromkiota command. The .kiota folder contains essential files like workspace.json, apimanifest.json, and OpenAPI descriptions which are required for generating and updating plugins and clients.

  2. Decide on Approach for Adaptive Cards Re-generation:

    • Automatically replacing adaptive cards during re-generation might simplify updates but may override custom edits.
    • Alternatively, maintain a separate file for adaptive cards to avoid overriding custom changes, although this will require manually adding new endpoints.
  3. Establish Process for Handling Updates Post-Regeneration:
    Determine whether to call fx-extension.createprojectfromkiota with updated content or introduce a new command specifically for regeneration.

Actionable Steps

  1. Update the .kiota Folder Path:
    Ensure that the .kiota folder path is included in the regeneration command. This can be done by passing the path as a parameter when calling the fx-extension.createprojectfromkiota command.

  2. Review the Regeneration Process:

    • Check if there are any manual steps required for updating conversation starters.
    • Consider implementing a custom script or process to handle the updates if TTK does not automatically update them.
  3. Contact Support or Report the Issue:
    If the issue persists, consider reaching out to the support team or reporting the issue on the GitHub Issue Tracker for Teams Toolkit. Provide detailed information about the steps you have taken and the specific issues you are encountering.

Relevant Links

  • GitHub Issue #12489: Discusses the integration of Kiota with Teams Toolkit and handling adaptive cards re-generation.

By following these steps and ensuring that the .kiota folder path is included in the regeneration command, you should be able to resolve the issue with DAs conversation starters not being updated.

If you need further assistance, please provide more details about your setup and the exact steps you are following to regenerate the plugin. This will help in providing a more specific solution.


Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs attention This issue needs the attention of a contributor. label Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs attention This issue needs the attention of a contributor.
Projects
None yet
Development

No branches or pull requests

1 participant