v1.5.0

Overview

The purpose of Enterprise Data Exchange (DEX) Upload release version 1.5.0 is to update upload configurations for data streams, add version 1 sender manifest metadata values to version 2 metadata fields, add the version 2 metadata configuration folder structure, add file copy functionality to routing storage, add Processing Status API integration, add Retry functionality, and add Replay functionality.

New Features

• Version 2 sender manifest configuration folder structure
• Version 1 sender manifest metadata values to version 2 metadata fields
• File copy functionality to routing storage accounts
• Processing Status API integration
• Retry functionality
• Replay functionality
• Upload configurations for the DAART data stream
• Remove file copy EDAV target from the CELR data stream

v1.4.1

Overview

The purpose of Enterprise Data Exchange (DEX) Upload release version 1.4.1 is to enhance telemetry through integration with the Processing Status API, enhance resiliency through retry/replay capabilities for our post-processing component, and publish configurations for onboarding the AIMS CELR use case.

Infrastructure Changes

• Renaming of Upload Processor function app
• Infrastructure to support retry/replay functionality
• Application settings to support connection to Processing Status API
• Deployment of blue/green slots to the Upload Processor function app

v1.2.3

Added descriptions for the functions in the repo
Routing Integration: copy to routing changes
Configured test event to send files to routing
Metadata update for NDLP accepted values
Added integration tests suite to upload repo
Metadata configuration changes for routing
Integrate app insight Bulk Upload Processor
Updated log level from error to information
Unit test for bulk upload
Metadata definitions added to summary table ( tus/file-hooks/metadata-verify/definitions/readme.md )

1.2.2

• NDLP APL historical data configuration (#159)
• Changing all upload configs of NDLP to not append clock ticks to the filename (#153)
• Implementation of printing exception stack trace for increased visibility into error details (#162)
• Updates to OpenAPI specifications (#160)
• Workflow refactoring for upload configurations (CI/CD) (#158)
• Addition of workflow for upload configurations (CI/CD) (#156)

1.2.1

• Fix for ndlp sending data without filename in metadata ( TUS post-receive hook )
• Create upoad root folder in edav ( bulk upload processor )
• Add new NDLP metadata and upload configs ( TUS file hooks: metadata-verify, upload-configs )
• aims-celr configurations ( TUS file hooks: metadata-verify, upload-configs )

v1.2.0

• Added upload database sync function to log each upload in the persistent storage ( Cosmos DB )
• Added Tus Hooks support to update upload status
• Added Supplemental API Function App to retrieve the status of an upload
• Added SAMS scopes
• Changes made to the APIM policy, enabling users with specified scopes to access particular functionality
• Added Metadata Configuration changes to support more use cases

v1.0.2

[1.0.2] - 2023-04-27

• Temporary hotfix to allow NDLP file uploads to work. IZGW is sending meta_ext_filename, but not filename in the metadata, which is failing in the bulk file upload function app. Temporary solution is to allow either field, but long-term fix will be to require 'filename' metadata field at time of upload.

v1.0.1

[1.0.1] - 2023-04-14

• HOTFIX to update the NDLP routine immunization required metadata fields to include meta_ext_submissionperiod

v1.0.0

[1.0.0] - 2023-04-04

• Created pre-create tus hook and associated JSON configuration files to support program and event specific metadata validation checks before an upload can proceed
• Created an Azure Function app for supporting bulk file uploads, whose purpose is to combine the tus payload and info files, copy the resultant combined blob file to DEX and EDAV storage accounts
• Github worker files for CI/CD of the tusd pre-create and function app