You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Dapr Java SDK has significantly improved support for Spring Boot. It's time to integrate Dapr's secret store and configuration as a backend for Spring Cloud Config.
The currently popular method for importing cloud config is through the spring.config.import configuration. According to the specification, a prefix is required. Since Dapr has two types of configurations (secret store and configuration), it might be necessary to distinguish between these two.
By the way, Dapr Configuration api supports subscribe update bot Secret Store is not according to the code. So do secret store need to be refresh?
Additionally, because cloud config runs during the bootstrap phase, it's not possible to use @Autowired to generate a DaprClient; it needs to be created manually. Whether users are allowed to import configurations different from the @Autowired DaprClient during this period is also a topic worth discussing.
Finally, how to handle cases where the corresponding data is not retrieved (e.g., throwing an error directly, running without configuration, or updating after going live) is another area that needs discussion.
The text was updated successfully, but these errors were encountered:
…dcoded prefix(dapr#1225)
create a public static final value PROPERTY_PREFIX in DaprClientProperties
change the prefix value in the ConfigurationProperties to DaprClientProperties.PROPERTY_PREFIX
Dapr Cloud Config rely on that.
Signed-off-by: lony2003 <[email protected]>
lony2003
added a commit
to fangkehou-team/java-sdk
that referenced
this issue
Mar 4, 2025
…of Spring Cloud Config(dapr#1225)
Originally from https://github.com/fangkehou-team/dapr-spring, this library created a backend of SpringCloudConfig just like SpringCloudVault.
The original library only uses secret store as config store api is not stable at that time.
As the configuration api is stable now, the config loader using that api would be implemented later.
Signed-off-by: lony2003 <[email protected]>
Describe the proposal
Currently, the Dapr Java SDK has significantly improved support for Spring Boot. It's time to integrate Dapr's secret store and configuration as a backend for Spring Cloud Config.
The currently popular method for importing cloud config is through the spring.config.import configuration. According to the specification, a prefix is required. Since Dapr has two types of configurations (secret store and configuration), it might be necessary to distinguish between these two.
for example:
dapr:secret:dapr-config-example.properties?refreshEnabled=true
dapr:config:dapr-config-example.properties?refreshEnabled=true
By the way, Dapr Configuration api supports subscribe update bot Secret Store is not according to the code. So do secret store need to be refresh?
Additionally, because cloud config runs during the bootstrap phase, it's not possible to use
@Autowired
to generate a DaprClient; it needs to be created manually. Whether users are allowed to import configurations different from the@Autowired
DaprClient during this period is also a topic worth discussing.Finally, how to handle cases where the corresponding data is not retrieved (e.g., throwing an error directly, running without configuration, or updating after going live) is another area that needs discussion.
The text was updated successfully, but these errors were encountered: