Skip to content

Conversation

@CasperGN
Copy link
Contributor

@CasperGN CasperGN commented Dec 16, 2025

Description

Allow Dapr Agents to discover default named stores for wf, pubsub, state and registry. This allows an agent to be started without any of these in its configuration. Upon start it will query the metadata api for available stores and if the following are returned:
agent-registry -> set the registry statestore if none provided
agent-statestore -> set the agent memory statestore if none provided
agent-wfstatestore -> set the DurableAgents wf statestore if none provided
agent-pubsub -> set the agent pubsub if none provided.

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR closes: N/A

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

Note: We expect contributors to open a corresponding documentation PR in the dapr/docs repository. As the implementer, you are the best person to document your work! Implementation PRs will not be merged until the documentation PR is opened and ready for review.

…agent-..' for -registry, -wfstatestore, -pubsub and -statestore. Set these if available a no other component provided

Signed-off-by: Casper Nielsen <casper@diagrid.io>
Signed-off-by: Casper Nielsen <casper@diagrid.io>
@CasperGN CasperGN requested review from a team as code owners December 16, 2025 12:11
@bibryam
Copy link
Collaborator

bibryam commented Dec 16, 2025

Casper, can you show here one/two examples of minimalistic agent configuration and what will be the default components the agent will be looking for? What happens if components are not present?

@CasperGN
Copy link
Contributor Author

Absolutely @bibryam i'll push that to dapr/docs

Copy link
Collaborator

@sicoyle sicoyle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM - thank you 🙌 can you pls update the documentation for these fields to denote these new defaults?

@CasperGN
Copy link
Contributor Author

Overall LGTM - thank you 🙌 can you pls update the documentation for these fields to denote these new defaults?

It's in the dapr/docs#4979 PR 🤝

@CasperGN CasperGN requested a review from sicoyle December 16, 2025 15:31
@sicoyle sicoyle merged commit ab4e7fc into dapr:main Dec 16, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants