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
If I configure a pointer to Azure Key Vault values from within Azure App Configuration, it would be useful if the dapr Azure App Configuration binding supported automatically turning those references into values.
As things stand right now, when I get a value from configuration that is mapped to an Azure Key Vault, it returns a JSON structure which represents a pointer to the Key Vault Resource.
This is undesirable as I'm then forced to use the Azure SDK to dereference that Key Vault pointer, thus breaking the dapr abstraction. 🪄
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
If I configure a pointer to Azure Key Vault values from within Azure App Configuration, it would be useful if the dapr Azure App Configuration binding supported automatically turning those references into values.
As things stand right now, when I get a value from configuration that is mapped to an Azure Key Vault, it returns a JSON structure which represents a pointer to the Key Vault Resource.
This is undesirable as I'm then forced to use the Azure SDK to dereference that Key Vault pointer, thus breaking the dapr abstraction. 🪄
The text was updated successfully, but these errors were encountered: