Skip to content

Latest commit

 

History

History
69 lines (56 loc) · 4.88 KB

BlobExtensions.md

File metadata and controls

69 lines (56 loc) · 4.88 KB

Blob Extensions

Behaviors

This repository contains the following behaviors:

Processors

This repository contains the following processors:

Commands

Blob extensions depend on blob commands, which represent the actual extension implementation:

Options

Blob commands are controlled using BlobOptions<TMessage>.

The same option can have different requirements within the scope of different commands. Options requirements are as follows:

  • Required: the value is required and an exception will be thrown if one is not supplied
  • Default: the value is required and a default will be provided if one is not supplied
  • Optional: the value is optional and will be used if one is supplied, ignored otherwise
  • Ignored: the value is not used by the command and supplying one will have no effect

Options and their requirements are described in the following table:

Option Description Upload Delete Download
IsEnabled true to enable execution of the extension, false to disable it Default 1 Default 1 Default 1
BlobClient The blob client against which the operation is executed Required Required Required
BlobContent The System.BinaryData containing the content to upload Default 2 Ignored Ignored
BlobHeaders The standard HTTP header system properties to set for the blob Default 2 Ignored Ignored
Metadata Custom metadata to set for the blob Optional Ignored Ignored
Downloaded The event that is raised after the blob is downloaded Ignored Ignored Optional

Footnotes

  1. false 2 3

  2. the message content is serialized as a JSON object and the Content-Type header is set to application/json 2