Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. .Net Core SDK

  2. .Net IDE of choice

  3. Access to the SkySync DryvIQ SDK packages

  4. SkySync DryvIQ SDK custom project template

  5. Basic understanding of creating a SkySync DryvIQ Platform extension


Getting Started

The SkySync DryvIQ Platform allows users to connect to on-premise and cloud storage platforms and orchestrate the content contained within those platforms. In order to orchestrate the content, SkySync DryvIQ will create a pipeline that facilitates pulling content from a source and transferring it to a destination. This pipeline can be configured based on user-configured options and available custom extensions. This creates an opportunity for extension developers to contribute to this pipeline to facilitate custom behavior such as manipulating permissions or custom metadata or transforming content from one format to another. In fact, a large majority of functionality within the transfer engine is built using this same extension mechanism. 


Creating Your First Transfer Extension

...

The first step is to modify our CustomServiceExtension class, which derives from IServiceCollectionExtension. Extensions of this type are automatically picked up and called while SkySync DryvIQ is starting up. This allows extension developers to register services with the same dependency injection container that SkySync DryvIQ uses. In order to modify the transfer pipeline, we first need to get access to it. This is required regardless of how we want to extend the transfer engine. We do that by adding a transfer pipeline extension.

...

During development of this extension, it is recommended to just build the extension using dotnet build, which will build your extension in the Debug configuration as well as copy the extension into the appropriate directory on your machine for SkySync DryvIQ to pick it up if you have a local copy that you can use to test live within the product. However, once you are ready to deploy this extension to customers then you will want to package the extension as a NuGet package (.nupkg file) using dotnet pack --configuration Release and deploy it to a SkySync DryvIQ instance.