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
Currently, Provision Watchers support regex matching for identifiers, but not for blockingIdentifiers.
In edgexfoundry-holding/device-onvif-camera, an example would be to create a provision watcher for any ONVIF device that is unknown. The idea would be to match any ONVIF camera without a Manufacturer attribute.
Unfortunately because it is already implemented using pure string matches, switching to regex could cause unintended side-effects. One option is to use a function that implements exact regex match (versus substring match) (ie. equivalent to ^regex$).
Another option would be to make it an explicit extra field, like so:
Create a provision watcher that blocks all Manufacturer values that are already defined in other provision watchers. This is harder to keep track of, as it would need to be updated on a per-install basis based on the other registered provision watchers.
🚀 Feature Request
Description [REQUIRED]
Currently, Provision Watchers support regex matching for
identifiers
, but not forblockingIdentifiers
.In edgexfoundry-holding/device-onvif-camera, an example would be to create a provision watcher for any ONVIF device that is unknown. The idea would be to match any ONVIF camera without a
Manufacturer
attribute.Describe the solution you'd like
Unfortunately because it is already implemented using pure string matches, switching to regex could cause unintended side-effects. One option is to use a function that implements exact regex match (versus substring match) (ie. equivalent to
^regex$
).Another option would be to make it an explicit extra field, like so:
Describe alternatives you've considered
Create a provision watcher that blocks all
Manufacturer
values that are already defined in other provision watchers. This is harder to keep track of, as it would need to be updated on a per-install basis based on the other registered provision watchers.The text was updated successfully, but these errors were encountered: