Open ScottArbeit opened 5 months ago
@philliphoff do you have some bandwidth to take a look at this?
@ScottArbeit Would you be able to share a more complete Dapr sidecar log-level debug log? Does it make a difference if you were to use AddDaprComponent("actorstorage", "state.azure.cosmosdb", /* ... */)
instead of AddDaprStateStore()
?
@davidfowl, I'm looking for a way to set this by code.... I thought Aspire was our escape from yaml!
I can't get any DAPR components from component definitions in a local folder to load either . I am using builder.AddDaprStateStore and builder.AddDaprComponent and neither seems to work.
Is this supposed to work or is it still in progress?
I can't get any DAPR components from component definitions in a local folder to load either . I am using builder.AddDaprStateStore and builder.AddDaprComponent and neither seems to work.
@adrobson Can you provide/show a repro project?
@philliphoff. Ignore my previous question. I can get Dapr components working now. I was not doing it correctly.
Hi! I could use another set of eyes on this... I'm converting a Dapr project from Kubernetes to Aspire, and I'm getting
Have you set the - name: actorStateStore value: \"true\" in your state store component file?
, when, indeed, I have.AppHost\Program.cs
The relevant bits from
AppHost\Program.cs
are:Dapr configuration
I'm configuring the state store with
actorstorage - local.yaml
, which is identical to what I configure Kubernetes with. I do setactorStateStore
in it:Dapr starts correctly
The log looks good:
Sad trombone
Unfortunately, when I test my code, I get
Have you set the - name: actorStateStore value: \"true\" in your state store component file?"
from Dapr:So...
Is there anything in Aspire's Dapr support that could be causing this?