For the fun of it I tried to run 24.6.1 in the docker compose dev environment. After some errors I came to the discovery that awx is dependant on django-ansible-base. The branch is main(or devel) and that repo has been getting re archtecture commits. So building 24.6.1 is broken unless you “guess” an old branch to use
So maybe to take into account for the the re-archtecture.
Version lock/tag … Required git repos like receptor, django-ansible-base, ansible-ui when you do a release
So,
Do you have already a starting point where us, as community, can maintain a fork of awx with package updated and no new features?
I was looking for a place to post this too. I forked devel and there are imports of ansible_base that break tests because the dependency is now ansible. If we’re wanting to make a PR should we update this or is it fixed in the re-architecture somewhere?
@kjamaal thanks for looking at this. Could you please raise a PR against the existing ansible/awx repo.
Thanks
It’s less of a “guess” than it is to find a release/tag/commit for required git repos around July 2nd, 2024. In django-ansible-base’s case, v2024.5.31 is the closest release tag (though I’m sure some newer tags would work too).
But yes, this would be part of the “patching” that would need to be done to maintain the AWX 24.6.1 release for subsequent builds and package upgrades.
The 24.6.1 tag would be where I would start.
Dependency wise, you can look at the date of 24.6.1, and look at the hash of the dependency, so for django-Ansible-base that would be Release v2024.7.1 · ansible/django-ansible-base · GitHub. Not an exact science, though should be close enough.
hooray for calver 
(such a good change)
PS: when will receptor start using calver?
I just realized I was looking at AWX’s 24.6.1 tag like it was calver (it isn’t) and found the closest tag to the first of June even though I knew I needed to find the one closest to the second of July (which is what @gundalow found).
Hi @Denney-tech,
Will this new architecture you are designing for AWX require us to install a new product in which we have to reprogram the playbooks? Or will we be able to export/import what we have today?
I’m worried about having to start over from scratch as if it were a new SW.
To reiterate, I am a fellow community member, not a Red Hat employee.
As far as I am aware, the new architecture should work the same with your current Ansible playbooks/projects, etc, so export/import migrations should be fine.
The installation/deployment of AWX might be different, depending on how you deploy in the first place, but you will probably be able to do an inplace upgrade without needing to do an export/import (though you should always have good backups and a DR strategy).