#390 Add scenario field to the database + migration script
Merged a month ago by vmaljulin. Opened 2 months ago by vmaljulin.
vmaljulin/waiverdb RHELWF-1854  into  master

@@ -0,0 +1,22 @@ 

+ """Add scenario field to the database

+ 

+ Revision ID: 3868a8118458

+ Revises: f6bc296ba966

+ Create Date: 2020-10-20 18:08:50.709804

+ 

+ """

+ 

+ # revision identifiers, used by Alembic.

+ revision = '3868a8118458'

+ down_revision = 'f6bc296ba966'

+ 

+ from alembic import op

+ import sqlalchemy as sa

+ 

+ 

+ def upgrade():

+     op.add_column('waiver', sa.Column('scenario', sa.String(length=255), nullable=True))

+ 

+ 

+ def downgrade():

+     op.drop_column('waiver', 'scenario')

@@ -50,6 +50,7 @@ 

      proxied_by = db.Column(db.String(255))

      product_version = db.Column(db.String(200), nullable=False)

      waived = db.Column(db.Boolean, nullable=False, default=False)

+     scenario = db.Column(db.String(255), nullable=True)

      comment = db.Column(db.Text)

      timestamp = db.Column(db.DateTime, default=datetime.datetime.utcnow)

      __table_args__ = (

no initial comment

Build 0c6477e FAILED!
Rebase or make new commits to rebuild.

Seems like the CI failed running the tests, could you check?

Is there a card for the change? If yes, could you add it to the commit message?

Add tests to get/set scenario in DB.

Shouldn't this be waiverdb/alembic?

Any reason to uncomment this? Did the default change?

Shouldn't this be waiverdb/alembic?

No, it's not working that way

Seems like the CI failed running the tests, could you check?

Some LDAP failures, not sure why (but probably related to previous change). I'll try to fix it.

rebased onto f51c7e3

a month ago

Build 39d207e FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
a month ago

Build 83b39ea FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
a month ago

Build 00b5372 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
a month ago

Build 9b00adf FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
a month ago

Build aea2cd6 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
a month ago

Build b172306 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
a month ago

Build c41fb77 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
a month ago

rebased onto 107190c

a month ago

2 new commits added

  • Add migration script for the scenario field
  • Add scenario field to the database
a month ago

Pull-Request has been merged by vmaljulin

a month ago

There are still no tests for the new DB field.