60953074e7
I think expiration should be pending on a proper way to do recurring tasks -- I'm personally in favor of a CLI command that can be run from a cronjob or systemd timer that will do things like auto-expire password reset requests and send the daily registration reports. Now that I'm thinking about it, this does need at least a rudimentary system to make sure that it actually expires. If the expiration is invalid at the time of reset, then the request can just be invalidated and deleted. There's no pressing need for automatic removal until it's implemented. Thoughts @willhockey20?
34 lines
939 B
Python
34 lines
939 B
Python
"""empty message
|
|
|
|
Revision ID: 8a0c9c00f04c
|
|
Revises: db38c3deb0b9
|
|
Create Date: 2023-01-03 16:59:23.201953
|
|
|
|
"""
|
|
from alembic import op
|
|
import sqlalchemy as sa
|
|
|
|
|
|
# revision identifiers, used by Alembic.
|
|
revision = '8a0c9c00f04c'
|
|
down_revision = 'db38c3deb0b9'
|
|
branch_labels = None
|
|
depends_on = None
|
|
|
|
|
|
def upgrade():
|
|
# ### commands auto generated by Alembic - please adjust! ###
|
|
with op.batch_alter_table('pw_reset_request', schema=None) as batch_op:
|
|
batch_op.add_column(sa.Column('user_id', sa.Integer(), nullable=False))
|
|
batch_op.create_foreign_key(None, 'user', ['user_id'], ['id'])
|
|
|
|
# ### end Alembic commands ###
|
|
|
|
|
|
def downgrade():
|
|
# ### commands auto generated by Alembic - please adjust! ###
|
|
with op.batch_alter_table('pw_reset_request', schema=None) as batch_op:
|
|
batch_op.drop_constraint(None, type_='foreignkey')
|
|
batch_op.drop_column('user_id')
|
|
|
|
# ### end Alembic commands ###
|