-
Notifications
You must be signed in to change notification settings - Fork 46
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
Dapr component schema #460
base: main
Are you sure you want to change the base?
Dapr component schema #460
Conversation
src/CommunityToolkit.Aspire.Hosting.Dapr/DaprDistributedApplicationLifecycleHook.cs
Outdated
Show resolved
Hide resolved
return await contentWriter(content).ConfigureAwait(false); | ||
} | ||
|
||
private string GetAppHostRelativePath(string componentName) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aside, we're creating a place to store things like this in 9.1, the aspire store.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice -Apphost relative? wanna point me to the code and I could update inline with that?
examples/dapr/CommunityToolkit.Aspire.Hosting.Dapr.AppHost/Program.cs
Outdated
Show resolved
Hide resolved
src/CommunityToolkit.Aspire.Hosting.Dapr/DaprComponentSecretAnnotation.cs
Show resolved
Hide resolved
src/CommunityToolkit.Aspire.Hosting.Dapr/DaprComponentSchema.cs
Outdated
Show resolved
Hide resolved
…notation.cs Co-authored-by: David Fowler <[email protected]>
…hef/CommunityToolkit-Aspire into dapr-component-schema
…gram.cs Co-authored-by: David Fowler <[email protected]>
…hef/CommunityToolkit-Aspire into dapr-component-schema
src/CommunityToolkit.Aspire.Hosting.Dapr/DaprComponentSchema.cs
Outdated
Show resolved
Hide resolved
Maybe if it is not to big of a no scope of this PR we should already start deviding dapr sidecar and component lifecycles to make our lifes easier later. So that we would have two LifecycleHooks and that everytime you have something like With this we will have an easier life if we need to consider the endpoints to generate the correct YAML files |
@paule96 my preference would be not to increase the scope of the my PR and I think the concept of separating lifecycle hooks needs further thought /design |
Closes #459
PR Checklist
Other information