This repository was archived by the owner on Nov 20, 2023. It is now read-only.

Description
Describe the bug
When setting up a tye.yaml with an Azure function app and the dapr extension, there is no sidecar started.
To Reproduce
- Create a new function app in an empty folder called
sample-app
.
- Initialize tye and change the tye.yaml contents to the following:
name: sample-name
extensions:
- name: dapr
log-level: debug
components-path: dapr-components/
services:
# - name: sample-app
# azureFunction: sample-app/
- Add a folder
dapr-components
to your root folder and optionally place configuration specs for dapr in there.
- Use
tye run
to start tye and note that there is no dapr sidecar started for the azure function project.
Further technical details
$ tye --version --> 0.11.0-alpha.22111.1+3edef5428949c518c078844d6438e5ba86fce600
If I understand correctly, Azure function projects are ignored in the Dapr Extensions:
|
var projects = context.Application.Services.OfType<ProjectServiceBuilder>().Cast<LaunchedServiceBuilder>(); |