You see the release workflow going on here right?
make a change that requires a reinstall
bump iiab_revision
add iiab_revision number and role to upgrade_roles

134 has the logic in bash to remove the role based on upgrade_roles from the iiab_state.yml file just like runrole --reinstall does for a single role. Could be done in other places but lets start with this in place to have something to test against?

This PR was tagged with "question" a week ago, with no question asked. What is the deal here?

Let's surface exactly these design/architectural questions and needs for this PR and others (PR #2511 and others) during our Thursday 10AM NYC IIAB Calls (http://minutes.iiab.io) so everybody can understand where changes like this are critically important, how they serve specific implementer/field communities's needs, medium-term versus long-term etc.

All hugely important questions.

Keeping in mind that IIAB 7.2 should ship this month with very few changes, if possible (i.e. most all structural/design changes should really target IIAB 8.0 at this point). No rule is completely hard & fast -- but as stated at http://minutes.iiab.io -- we should try to keep those remaining IIAB 7.2 pre-release changes bounded in these 3 rough categories: (if at all possible!!)

• Ansible 2.10 support Validate Ansible 2.10 expected 2020-08-13 [with simplified auto-installation of "Collections" ETA 2020-09-22 ?] #2479
• Friendlier install of new OSM Map Packs + Satellite Photos (with Admin Console integration as nec?)
• WiFi hotspot reliability issues if/as needed by Concerning 1 line install on Raspberry pi 3b+ [kolibri.service failed to start due to Ansible 2.9.12; 'ansible_userspace_architecture' is undefined; WiFi flaky due to RaspiOS kernel 5.4.51-v7+ #1333 and/or 3rd party 'hat' doing USB boot?] #2497 ?

The general idea is to use iiab_revision in conjunction with tagging|branching to denote an easy a point in time reference of the code-base without resorting to git hashes.

This goes into 7.2 or the freebies stop.

is the proposal to track revisions by role or by entire install?

By the role

@holta Get off your high horse you power freak.

Despite the childish attempt to block testing progress by reverting this commit /iiab/iiab-factory#134 proved to be a success http://sprunge.us/YlHp09 note the order of entries in /etc/iiab/iiab_state.yml the 3 roles were automatically upgraded as the new entries are below calibreweb_installed, the last role to possibly be installed on a machine that was first installed on July 20.