Fetching Keys from Azure App Config using metadata.label not returning appropriate response.

[dbauswel]

Fetching Keys from Azure App Configuration using metadata.label field does not work. Currently receiving a 404 response.
code snippet attached.

const config = await client.configuration.get(
            'azureappconfig',
            [key1],
            {
                metadata: {
                    label: yourEnv
                }
            }
        )

Note that making a direct call works.
/v1.0/configuration/azureappconfig?key=key1&metadata.label=yourEnv

[shubham1172]

Hi @dbauswel, the HTTP DaprClient does not support configuration so I guess you meant the gRPC DaprClient is throwing a not-found error? Are you able to make a direct gRPC request and get this data?

[tlund101]

Hi @dbauswel, the HTTP DaprClient does not support configuration so I guess you meant the gRPC DaprClient is throwing a not-found error? Are you able to make a direct gRPC request and get this data?

@shubham1172 I'm familiar with the issue, and this is correct. Both GetConfiguration and GetConfigurationAlpha1 from the proto file correctly return a key with the matching metadata label via gRPC request. Trying to use the gRPC DaprClient seems to ignore the metadata and returns a matching key without a label (if there is one, otherwise it logs a 404 error).

Passing an empty array to fetch all keys returns them all, and those that have labels show them in the metadata field that is returned.

[shubham1172]

Thanks for the insight @tlund101, it looks like it's the way the metadata is being passed.

Non-working scenario

js-sdk/src/implementation/Client/GRPCClient/configuration.ts

Line 59 in 5c2b40a

client.getConfiguration(msg, metadata, (err, res: GetConfigurationResponse) => {

Working scenario

js-sdk/src/implementation/Client/GRPCClient/state.ts

Line 142 in 5c2b40a

addMetadataToMap(msgService.getMetadataMap(), options.metadata);

We need to change it. Please let me know if any of you want to create a PR, else I will create one.

[tlund101]

Looks pretty straightforward, I'll take a look at it and test it on our end.