This PR migrates some PaaS classes into OSS, and attempts to consolidate the startup classes (and code) between OSS and PaaS. Previously there was one startup class in OSS for both normalization and fhirtransformation. Now, there is one startup class for normalization and one startup class for fhirtransformation which aligns with PaaS. These startup classes will be consumed in PaaS and can be subclassed if needed.
The only differences in PaaS should be:
inject different logging
inject an IAzureExternalIdentityCredentialProvider to connect to event hub and fhir service
inject health checks
For this iteration we are adding classes. Once we migrate to these new classes (nuget packages) in PaaS we will deprecate the code in .\iomt-fhir\src\console\Microsoft.Health.Fhir.Ingest.Console.csproj which will be no longer be needed.
One additional call out for OSS is that we are now using ResumableEventProcessor so that we can align on one event processor but in OSS we are not using any healthchecks. If we feel that the healthchecks should be migrated to OSS then I am open to that.
This PR migrates some PaaS classes into OSS, and attempts to consolidate the startup classes (and code) between OSS and PaaS. Previously there was one startup class in OSS for both normalization and fhirtransformation. Now, there is one startup class for normalization and one startup class for fhirtransformation which aligns with PaaS. These startup classes will be consumed in PaaS and can be subclassed if needed.
The only differences in PaaS should be:
For this iteration we are adding classes. Once we migrate to these new classes (nuget packages) in PaaS we will deprecate the code in
.\iomt-fhir\src\console\Microsoft.Health.Fhir.Ingest.Console.csprojwhich will be no longer be needed.One additional call out for OSS is that we are now using ResumableEventProcessor so that we can align on one event processor but in OSS we are not using any healthchecks. If we feel that the healthchecks should be migrated to OSS then I am open to that.