Skip to content
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.

Dapr extension not considering Azure function apps #1431

Open
maltegoetz opened this issue Jul 13, 2022 · 0 comments · May be fixed by #1612
Open

Dapr extension not considering Azure function apps #1431

maltegoetz opened this issue Jul 13, 2022 · 0 comments · May be fixed by #1612
Labels
bug Something isn't working

Comments

@maltegoetz
Copy link

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

  1. Create a new function app in an empty folder called sample-app.
  2. 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/
  1. Add a folder dapr-components to your root folder and optionally place configuration specs for dapr in there.
  2. 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>();

@maltegoetz maltegoetz added the bug Something isn't working label Jul 13, 2022
@Phiph Phiph linked a pull request Sep 28, 2023 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant