Bumps [Microsoft.Azure.Functions.Worker](https://github.com/Azure/azure-functions-dotnet-worker) from 1.16.0 to 1.17.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Azure/azure-functions-dotnet-worker/releases">Microsoft.Azure.Functions.Worker's releases</a>.</em></p> <blockquote> <h2>Microsoft.Azure.Functions.Worker 1.17.0</h2> <h2>What's Changed</h2> <h3>Microsoft.Azure.Functions.Worker (metapackage) 1.17.0</h3> <ul> <li>Nothing</li> </ul> <h3>Microsoft.Azure.Functions.Worker.Core 1.13.0</h3> <ul> <li>Nothing</li> </ul> <h3>Microsoft.Azure.Functions.Worker.Grpc 1.12.0</h3> <ul> <li>bumping grpc packages by <a href="https://github.com/brettsam"><code>@brettsam</code></a> in <a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/pull/1719">Azure/azure-functions-dotnet-worker#1719</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Azure/azure-functions-dotnet-worker/compare/1.16.0...1.17.0">https://github.com/Azure/azure-functions-dotnet-worker/compare/1.16.0...1.17.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/68cb6ca7e3c93753d76d31eaf982a7584672b28a"><code>68cb6ca</code></a> bumping grpc packages (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1719">#1719</a>)</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/f3b49344ea3ce15a7aa7ac54db5b456dd80b7a6d"><code>f3b4934</code></a> Reset release notes for Worker and SDK packages</li> <li><a href="https://github.com/Azure/azure-functions-dotnet-worker/commit/6910409b8b3090215c4807f392820aa8c4396258"><code>6910409</code></a> [Source Gen] Add retry options diagnostic descriptors (<a href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1683">#1683</a>)</li> <li>See full diff in <a href="https://github.com/Azure/azure-functions-dotnet-worker/compare/1.16.0...1.17.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Semantic Kernel Service API (For Learning Samples)
Watch the Service API Quick Start Video.
This service API is written in C# against Azure Function Runtime v4 and exposes some Semantic Kernel APIs that you can call via HTTP POST requests for the learning samples.
!IMPORTANT
This service API is for educational purposes only and should not be used in any production use case. It is intended to highlight concepts of Semantic Kernel and not any architectural security design practices to be used.
Prerequisites
Azure Functions Core Tools installation is required for this service API to run locally.
Running the service API locally
Run func start --csharp from the command line. This will run the service API locally at http://localhost:7071.
Two endpoints will be exposed by the service API:
- InvokeFunction: [POST]
http://localhost:7071/api/skills/{skillName}/invoke/{functionName} - Ping: [GET]
http://localhost:7071/api/ping
Working with Secrets
We need keys to work with various aspects of the project including accessing openAI models. This opens up the possibility of exposing keys in commits. There are a couple of options to safeguard developers from exposing keys. Outside of using the dotnet's users-secrets and environment variables, we've also added *.development.config to the .gitignore if developers want to use config files for secret storage.
Next steps
Now that your service API is running locally,
let's try it out in a sample app so you can learn core Semantic Kernel concepts!
The service API will need to be run or running for each sample app you want to try.
Sample app learning examples:
- Simple chat summary (Recommended) – learn how basic semantic functions can be added to an app
- Book creator – learn how Planner and chaining of semantic functions can be used in your app
- Authentication and APIs – learn how to connect to external API's with authentication while using Semantic Kernel
- GitHub Repo Q&A – learn how Memories and Embeddings can be used in your app
