On Thu, May 8, 2025, at 7:22 AM, Dmitriy Rabotyagov wrote:
I'm pretty sure it is.
There is no point in the Git tree, where we can say - ok, now use a module. As either it will be broken before the switch, or with it. Actually it is not required, but only if it's the single project doing such migration. As in case there're 2 of them, it will cause circular dependency right away for the integration test.
So the way to make all play nicely, is to use SHA/versions where both modules and scripts are present, switch over, profit.
And as you said - switching to using modules is a no brainer, it is a trivial patch in fact for deployment. But only if there is a way to not have to nucke CI in between.
If uwsgi has the ability to directly call the application factory method (init_application() in [1]) then you should be able to start doing that without any changes to designate. That said I have found documentation for gunicorn and granian indicating this is possible, but have not been able to find an indication that uwsgi can do this. If this isn't possible, then I agree we probably need to keep the old and new systems in place for some amount of time to make the transition simpler.
[1] https://review.opendev.org/c/openstack/designate/+/902846