Open HashTagDotNet opened 4 years ago
Hi @HashTagDotNet similar to #212, this is by design. Using wildcard and comma together is not a supported filter. We, however, need improvement of the documentation for easier discovery of this information.
https://github.com/Azure/AppConfiguration/blob/master/docs/REST/kv.md#filtering
Perhaps this information could be returned in the API response error message. That might save somebody else a significant amount of work.
"Invalid character" doesn't give me much more information than "something really bad happened".
Suggestion: { "type":"https://azconfig.io/errors/invalid-argument", "title":"Invalid request parameter 'key'", "name":"key", "detail":"key(14): Invalid character. Delimited wild-card key selectors are not supported. Make separate calls to the service. See your client's documentation for more details", "pos":14, "status":400} }
I'm sure you can't comment, but will being made to make multiple calls to the API affect the cost of using this service? I'm assuming there might be a per-call or per-key type of charge in the future.
Thanks for the suggestion @HashTagDotNet. We will consider it.
The pricing plan can be found at https://github.com/Azure/AppConfiguration-Announcements/issues/2. The filtering support could be enriched in the future. The config provider library is making necessary calls based on what is currently supported by the REST API.
Microsoft.Extensions.Configuration.AzureAppConfiguration, Version=3.0.0.0, Culture=neutral,
When I use a '*' wild card in any
AzureAppConfigurationOptions.Select()
with multiple comma delimited segments, I get an error.Request
Response
Work Around
Use separate
options.Select()
statements for each wild card selector. This work around results in separate calls to Azure for eachoptions.Select()
definition.