wwlwpd
This adds the git info to the environment, `run.properties` via `writeProperties.sh`, `asgs-info`, `show version`, adds a health check, and provides a file called `$SCRIPTDIR/VERSION` that can be updated with a...
If it's not a git repo, `asgs-info` just warns _ASGS is not a git repo._ and the envars exist but are not set (empty). `asgs-info -v` always pulls from `$SCRIPTDIR/VERSION`...
@jasonfleming this is ready for review. I have not started ASGS to confirm `run.properties`, but please do a code review and exercise `asgs-info`, including updating the `VERSION` file to see...
> Overall, this looks great and I am looking forward to having this info readily available interactively as well as in the status and run metadata. As far as dynamically...
> I agree that we would not normally expect the `VERSION` file to change after `asgsh` is started. So I wasn't sure if that was a valid concern. But I...
@jasonfleming this is ready for another look.
example of `run.properties`, (note: line breaks are due to small screen) The most recent tweak, I made `asgs.version` not contain the commmit, that's in `asgs.git.commit`.
@jasonfleming just wanted to remind you to please review this.
@jasonfleming sorry I missed notification for these comments. Yes, I can take care of all those. Great feedback, thanks!
> @wwlwpd thank you ... I am looking at the content of the `run.properties` file, and I think we can remove everything up to the first `:` in the output...