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
For Blob we will need the Blob data contract resource as well to be able to bind a data type to bucket.
This help in enabling quite some IoT/IoMT flows as well where say data via Data Broker is to be routed to Blob bucket and devices can go agnostic and post data on data type and bucket / rest details can be managed via this resource and routing (or re-routing) can be done as needed, w/o having need to update device space or firmware.
For Blob we will need the
Blob data contract resource
as well to be able to bind adata type
tobucket
.This help in enabling quite some IoT/IoMT flows as well where say data via Data Broker is to be routed to Blob bucket and devices can go agnostic and post data on
data type
and bucket / rest details can be managed via this resource and routing (or re-routing) can be done as needed, w/o having need to update device space or firmware.Current equivalent exist in MDM
hsdp_connect_mdm_blob_data_contract
& need to be updated with Blob API https://www.hsdp.io/documentation/blob-repository/api-documents/blob-repository-api#/BlobDataContract/post_connect_blobrepository_configuration_BlobDataContractThe text was updated successfully, but these errors were encountered: