Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
alembic 1.2.0 broke the alembic.command.stamp() revision parameter #601
Trying to use OpenStack services with alembic 1.2.0 (currently 1.1.0 is used) is breaking a lot of services with (Ironic example):
Looks like the
I wonder if it would be possible (until 2.0.0 comes up) to support
Also oslo.db is affected. It tries to use the
Added new ``--purge`` flag to the ``alembic stamp`` command, which will unconditionally erase the version table before stamping anything. This is useful for development where non-existent version identifiers might be left within the table. Additionally, ``alembic.stamp`` now supports a list of revision identifiers, which are intended to allow setting up muliple heads at once. Overall handling of version identifiers within the ``alembic.stamp`` command has been improved with many new tests and use cases added. Fixes: #473 Change-Id: If06501b69afae9956df3d0bcd739063fb8042a02
someone actually noted that I changed this name, and I asked, you're not actualy using the positional argument as a kw are you, and they said no, and I was like, OK, great. But then here we are. Alembic is actually tested against neutron and oslo.db, I can add more alembic-using projects like ironic since nova/keystone have unfortuantely never switched.
There's a decorator I can use to allow for both kw args but also it should be passed positionally.
* Update requirements from branch 'master' - Merge "Skip alembic 1.2.0" - Skip alembic 1.2.0 Version 1.2.0 changed the alembic.command.stamp() method which no longer accepts a "revision" parameter (not it accepts a "revisions" parameter). Upstream bug is: sqlalchemy/alembic#601 Change-Id: Iec1f21e544b6efc17401c0cb9ff7472f020a7dc3