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

How do you load/define dapr components? #49

Open
onionhammer opened this issue Nov 28, 2023 · 5 comments
Open

How do you load/define dapr components? #49

onionhammer opened this issue Nov 28, 2023 · 5 comments

Comments

@onionhammer
Copy link

onionhammer commented Nov 28, 2023

I'm not seeing it in the dapr sample, it seems to just start a sidecar that does nothing?

The sample could, for example, demonstrate using a cron binding

Edit:

This is how

    .WithDaprSidecar(new DaprSidecarOptions
    {
        AppId = "your-api",
        ResourcesPaths = [
            "../your/components",
        ],
    });
@onionhammer onionhammer changed the title How do you load dapr components? How do you load/define dapr components? Nov 28, 2023
@DamianEdwards
Copy link
Member

@paulyuk thoughts?

@davidfowl
Copy link
Member

@philliphoff is working on this right now!

@danmoseley
Copy link
Member

@philliphoff is this still relevant

@philliphoff
Copy link

philliphoff commented Jan 16, 2024

@danmoseley The Dapr sample in this repo doesn't require any components as it uses only method invocation. The Dapr sample in the dotnet/aspire repo does, as it makes use of pub-sub and state-store components.

What's the thinking on where proper Aspire samples ought to live, here or in the aspire repo itself? If here, should we move over the one from the aspire repo? It seems like it'd be an extra headache to try to maintain both. (See related #82.)

@DamianEdwards
Copy link
Member

What's the thinking on where proper Aspire samples ought to live, here or in the aspire repo itself? If here, should we move over the one from the aspire repo? It seems like it'd be an extra headache to try to maintain both. (See related #82.)

Proper samples live in this repo. We just renamed the directory in the other repo to "playground" to better describe its purpose (i.e. to make it easier for folks working on Aspire itself to have apps that use features in the repo).

I'd update the sample in this repo to include showing relevant features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants