Feature request: Ability to pick see a new package based on build number
rgeniesse opened this issue · 1 comments
As a follow up to being able to have the repository channel be configurable, we have ran into another scenario where it would be beneficial to call out the build number to look for inside the package.
During the Sensu Go QA process for a new release candidate, we are using this Ansible collection to upgrade a long running instance of Sensu Go to mimic customer environments. This lets us both look for possible issues that may not be seen on environments spun up just for QA and also learn about the Ansible collection for supporting customers that are or may eventually use it.
When we upgrade our long running instance as part of the QA process, if bug is found, currently only the version of the package is looked at by Ansible. The new release candidate only has the build number changed as fixes are put in, so Ansible doesn't see anything "new". While not all bugs will warrant another upgrade of this long running instance, as it stands I have to downgrade to the old version and re-upgrade to the new build to get a new release candidate installed.
Is it possibly to have Ansible, either in the collection or in Ansible core, to detect the build number of the package? It would appear for at least yum the release field is what contains this:
Name : sensu-go-backend
Arch : x86_64
Version : 5.15.0
Release : 7782
Size : 35 M
Repo : installed
From repo : sensu_stable
Summary : Sensu Go Backend
URL : https://sensu.io
License : Proprietary
Description : Sensu Go Backend
I took a quick look around and only found this area to have that added:
https://github.com/sensu/sensu-go-ansible/blob/master/roles/install/tasks/main.yml#L10-L17
But I don't know how you would default the build number or maybe you would need a conditional that if it is null, don't look at it. Also don't know if there are python things to make this worth either.
This issue was meant for a completely different repo.