Add reporting of git version (last commit) by egeria server

[planetf1]

It would be really useful to be able to check what exact version an egeria server is at when debugging problems / capturing info or during development

Some tools like helm make his easy to check on the command line - and will report server and client version - for example:

➜  atlas git:(helm32) ✗ helm version                                                                                                                                   git:(helm32|✚1
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

We could do something similar in Egeria -

• report git version as part of server origin?
• ensure version gets written to audit/debug output
• capture in client code ...

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[grahamwallis]

This information has been asked for in relation to Dino so it would be useful if we can capture more git version and build information that can be accessed through (prob.) the platform services API.

[planetf1]

In open-metadata-resources/open-metadata-deployment/docker/egeria I make use of a 'git-commit-id-plugin' to pull out some git information that is then fed into the docker build so that we have metadata stored within the image.

There's docs at https://github.com/git-commit-id/git-commit-id-maven-plugin/blob/master/maven/docs/using-the-plugin.md which show an example of creating a git.properties, that we could package up.

That all being said I'm continuing to find maven awkward in numerous areas. Gradle is work in progress, and it looks like another approach is viable there -> https://villim.github.io/get-git-commit-info-in-gradle with the key being the 'grgit' library

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.