Get FHIR Server Version

[davidegiacometti]

User story
Add an API to retrieve FHIR server version corresponding to the GitHub release that is deployed.

[Ivanidzo4ka]

https://www.hl7.org/fhir/capabilitystatement-definitions.html#CapabilityStatement.software
CapabilityStatement.software.version sounds like a good candidate to output that information.

We should probably put release information into that field.

[Ivanidzo4ka]

We actually using that field and populate it with Assembly.Version value.
Which we populate with AssemblySemVer see https://gitversion.net/docs/reference/variables

problem its not descriptive enough.

Suitable for .NET AssemblyVersion. Defaults to Major.Minor.0.0 to allow the assembly to be hotfixed without breaking existing applications that may be referencing it.

@brendankowitz Can we switch to AssemblySemFileVer instead?

Our first minor upgrade happened 3 days ago, so all versions looks like 1.0.0.0

[brendankowitz]

We set it here for the nuget packages and webdeploy files, but I don't think it gets set properly in the docker build.

fhir-server/build/jobs/build.yml

Lines 14 to 15 in 473baa5

	command: build
	arguments: '--configuration $(buildConfiguration) -p:ContinuousIntegrationBuild=true -p:AssemblyVersion="$(assemblySemVer)" -p:FileVersion="$(assemblySemFileVer)" -p:InformationalVersion="$(informationalVersion)" -p:Version="$(majorMinorPatch)" -warnaserror'

Our strategy is configured slightly differently atm in that we're only requiring recompilation on Major increments.

[Ivanidzo4ka]

nuget packages

Can we switch that build command to use assemblySemFileVer instead of assemblySemVer or maybe change assignment of assemblySemVer to same assignment we have for assemblySemFileVer

[Ivanidzo4ka]

Another option is not to use AssemblyVersion in capability statement, and use FileVersion instead.

[CaitlinV39]

AB#86147

[CaitlinV39]

@davidegiacometti we added this in PR #2294