With our new advanced filters, we’ve added data attribute filters and StringContains as an operator (among many others). Take a look and let us know what you think!
We will likely not add wildcards and regex for quite some time due to the compute and latency costs it would incur, however, we think, most of the use-cases described (and more) can be addressed with our new filters: https://docs.microsoft.com/en-us/azure/event-grid/event-filtering#advanced-filtering
1 voteDiego commented
There is, in SF Explorer you can go to you cluster (The first item on TreeView menu on left side), them select "Details" in the right pane, you should see SF version on "Code Version" in the list.
20 votesDiego commented
Hi, This suggestion is cool, would be welcome.
But you have other ways to accomplish this without duplicating the entire service as you suggested.
Are you aware that you can have multiple ConfigPackages?
You could use the default one (Config) to create the settings shared by all other 'instances', and create one for each specific service you need named as the servicename.
From you code, you could just resolve the packages using the service name:
Regarding the instanceCount and partitions, you can do the same through the defaultServices, create a copy of the service definition pointing to the same service with a different name, and use the application parameters to specify different instanceCount and partitions.
I know it is not the best solution, but can solve your problem for now.
This feature is a future planned item.
Audio Only scenarios are currently supported by live streaming pipeline, but not fully supported by Azure Media Player on DASH and on some platform with Smooth Streaming. You can use iOS native player to play audio only HLS output untill AMP gets the support.
We’ve added some custom configurable tiles such as; ‘markdown’ (allows custom markdown), ‘armData’ (will display data from a defined arm GET), and ‘armActions’ (creates a button which will create a user defined arm POST call)