Similarly to how we push the version in the heartbeat response, we should include the git hash. This helps with consumer trust and shows that the service published is indeed the one we build in the open.
Detailed overview
There should be an easy way to pull the Git hash from the Gradle script; with that hash value, we can push it into the generated.properties file together with the app version. The name can be something like git_sha
How the version is pulled into the project:
build.gradle.kts:128 - propertyGenerator task
Then, we should pull it further into the Configuration bean:
com.appifyhub.monolith.util.meta.BuildMetadata
And finally, we should include it in the heartbeat response:
Provide a brief summary of the planned work
Similarly to how we push the version in the heartbeat response, we should include the git hash. This helps with consumer trust and shows that the service published is indeed the one we build in the open.
Detailed overview
There should be an easy way to pull the Git hash from the Gradle script; with that hash value, we can push it into the
generated.propertiesfile together with the app version. The name can be something likegit_shaHow the version is pulled into the project:
Then, we should pull it further into the Configuration bean:
And finally, we should include it in the heartbeat response:
List the acceptance criteria
git_shaproperty is available in the Heartbeat responseInclude any additional notes (optional)
No response