How to manage additional resource for bulk data 2.0.0 in to bulk data 1.0.0

[jaydeep581990]

We are currently implementing Bulk Data 2.0.0 for Group Bulk Data Export. Previously, we were using Bulk Data 1.0.0, which worked as expected and passed the Inferno test tool validations.

With Bulk Data 2.0.0, a few additional resources are now required for Group Bulk Export in order to pass the Inferno tests (e.g., ServiceRequest, RelatedPerson, Specimen, etc.). These resources are already available in our system, and we plan to include them in the Group Bulk Export by updating the appsettings.json configuration and incorporating the necessary logic into our façade layer, as shown below:

"BulkDataExport": {
"RepeatPeriod": 60000, //ms
"AdditionalResources": [ "ServiceRequest", “RelatedPerson”, “Specimen”]
}

The challenge we’re facing is that the list of required resources differs between Bulk Data 1.0.0 and 2.0.0. While the newer resources are needed for 2.0.0, they are not required or present in the 1.0.0 implementation.
Since we use shared logic for bulk export in the façade layer, the question is: how can we determine which Bulk Data version the Inferno test is executing against—so that we can conditionally exclude the new resources when testing against Bulk Data 1.0.0?

For context, our façade implementation uses the CreateGroupSnapshot method from the IGroupBulkDataExportRepository interface in the Vonk.Core DLL. This method is common for creating the group resource snapshots used in both versions of the bulk export process.