Reference secrets in components for Dapr resources

[willtsai]

Overview of feature request

According the to Dapr documentation, in order to reference secrets for the spec.metadata section within the components definition you need to set the auth.secretStore field to specify the name of the secret store that holds the secrets if you are looking to reference something outside of the Kubernetes secret store.

However, the auth.secretStore field is not currently supported in the Radius Dapr Resources properties (e.g. Dapr pubsub properties and thus Radius users are not able to leverage this feature of Dapr components. This request is for this auth.secretStore field to be supported so that users may reference non-Kubernetes secrets for the Dapr spec.metadata.

Acceptance criteria

• Support is added for the auth.secretStore field in Radius.
• Additional property for auth.secretStore in Dapr Resource schema
• Documentation updated to reflect this.

Additional context

No response

Would you like to support us?

• [ ] Yes, I would like to support you

AB#12577

[radius-triage-bot[bot]]

:wave: @willtsai Thanks for filing this feature request.

A project maintainer will review this feature request and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[radius-triage-bot[bot]]

:+1: We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview