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

[USER STORIES] E2E Dev Ops Sample #6601

Closed
matthewbolanos opened this issue Jun 7, 2024 · 3 comments
Closed

[USER STORIES] E2E Dev Ops Sample #6601

matthewbolanos opened this issue Jun 7, 2024 · 3 comments
Labels
samples sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) wontfix This will not be worked on

Comments

@matthewbolanos
Copy link
Member

There should be a GitHub project that demonstrates how an AI and app development team can work together in a single mono-repo to create an enterprise application. The following process should be shown:

  1. AI developers can author prompts, agents, and descriptions for OpenAPI plugins using the VS Code extension (future)
  2. AI developers can perform offline ingestion of documents into a vector DB
  3. When the AI developer creates a PR, integration tests should run evaluations using benchmark data
  4. If the integration tests pass, the PR can be merged in
  5. App developers should be able to test the new AI assets in their code instantly
  6. App developers can use out-of-the-box reports to detect if non-functional requirements like performance are negatively impacted by the new AI assets using OpenTelemetry
  7. The enterprise app developers should have the ability to easily deploy the app to top Microsoft services: Azure Functions, Azure App Services, Azure Container Apps, etc.
  8. Once the app is live, they should be able to observe the same data using OpenTelemetry
@matthewbolanos matthewbolanos converted this from a draft issue Jun 7, 2024
@matthewbolanos
Copy link
Member Author

We should make this a codespace project to make it easy to get started

@evchaki evchaki added the sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) label Nov 5, 2024
@markwallace-microsoft
Copy link
Member

Closing as obsolete

@markwallace-microsoft markwallace-microsoft added the wontfix This will not be worked on label Dec 11, 2024
@RicardoNiepel
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
samples sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) wontfix This will not be worked on
Projects
Archived in project
Development

No branches or pull requests

4 participants