darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2025-12-13 00:32:16 -05:00
Code Issues Packages Projects Releases Wiki Activity
Files
19dcd7a48b6f06ea33bc1ee0635c34c8f9df199d
notifications-api/migrations/versions/0339_service_billing_details.py

40 lines
1.8 KiB
Python
Raw Normal View History

Add billing details fields to Service model and db table The fields are: Purchase order number - string field Billing contact name - text field to acommodate possible multiple contacts Billing contact email address - text field to acommodate possible multiple contacts Billing reference - string field All these fields are nullable. Notify platform admins will be able to check and edit those values in Service Settings section in Notify interface. This will help make billing tasks and reports simpler. Similar fields will also be added to Organisation model and db table.
2021-01-20 18:00:43 +00:00
"""
Revision ID: 0339_service_billing_details
Revises: 0338_add_notes_to_service
Create Date: 2021-01-20 17:55:46.555460
"""
from alembic import op
import sqlalchemy as sa
revision = '0339_service_billing_details'
down_revision = '0338_add_notes_to_service'
def upgrade():
# ### commands auto generated by Alembic - please adjust! ###
Rename billing contact email and name fields to plural So: 'billing_contact_email_address' becomes 'billing_contact_email_addresses' AND 'billing_contact_name' becomes 'billing_contact_names' This is to signify that each of those fields can contain numerous items
2021-01-25 17:53:22 +00:00
op.add_column('services', sa.Column('billing_contact_email_addresses', sa.Text(), nullable=True))
op.add_column('services', sa.Column('billing_contact_names', sa.Text(), nullable=True))
Add billing details fields to Service model and db table The fields are: Purchase order number - string field Billing contact name - text field to acommodate possible multiple contacts Billing contact email address - text field to acommodate possible multiple contacts Billing reference - string field All these fields are nullable. Notify platform admins will be able to check and edit those values in Service Settings section in Notify interface. This will help make billing tasks and reports simpler. Similar fields will also be added to Organisation model and db table.
2021-01-20 18:00:43 +00:00
op.add_column('services', sa.Column('billing_reference', sa.String(length=255), nullable=True))
op.add_column('services', sa.Column('purchase_order_number', sa.String(length=255), nullable=True))
Rename billing contact email and name fields to plural So: 'billing_contact_email_address' becomes 'billing_contact_email_addresses' AND 'billing_contact_name' becomes 'billing_contact_names' This is to signify that each of those fields can contain numerous items
2021-01-25 17:53:22 +00:00
op.add_column('services_history', sa.Column('billing_contact_email_addresses', sa.Text(), nullable=True))
op.add_column('services_history', sa.Column('billing_contact_names', sa.Text(), nullable=True))
Add billing details fields to Service model and db table The fields are: Purchase order number - string field Billing contact name - text field to acommodate possible multiple contacts Billing contact email address - text field to acommodate possible multiple contacts Billing reference - string field All these fields are nullable. Notify platform admins will be able to check and edit those values in Service Settings section in Notify interface. This will help make billing tasks and reports simpler. Similar fields will also be added to Organisation model and db table.
2021-01-20 18:00:43 +00:00
op.add_column('services_history', sa.Column('billing_reference', sa.String(length=255), nullable=True))
op.add_column('services_history', sa.Column('purchase_order_number', sa.String(length=255), nullable=True))
# ### end Alembic commands ###
def downgrade():
# ### commands auto generated by Alembic - please adjust! ###
op.drop_column('services_history', 'purchase_order_number')
op.drop_column('services_history', 'billing_reference')
Rename billing contact email and name fields to plural So: 'billing_contact_email_address' becomes 'billing_contact_email_addresses' AND 'billing_contact_name' becomes 'billing_contact_names' This is to signify that each of those fields can contain numerous items
2021-01-25 17:53:22 +00:00
op.drop_column('services_history', 'billing_contact_names')
op.drop_column('services_history', 'billing_contact_email_addresses')
Add billing details fields to Service model and db table The fields are: Purchase order number - string field Billing contact name - text field to acommodate possible multiple contacts Billing contact email address - text field to acommodate possible multiple contacts Billing reference - string field All these fields are nullable. Notify platform admins will be able to check and edit those values in Service Settings section in Notify interface. This will help make billing tasks and reports simpler. Similar fields will also be added to Organisation model and db table.
2021-01-20 18:00:43 +00:00
op.drop_column('services', 'purchase_order_number')
op.drop_column('services', 'billing_reference')
Rename billing contact email and name fields to plural So: 'billing_contact_email_address' becomes 'billing_contact_email_addresses' AND 'billing_contact_name' becomes 'billing_contact_names' This is to signify that each of those fields can contain numerous items
2021-01-25 17:53:22 +00:00
op.drop_column('services', 'billing_contact_names')
op.drop_column('services', 'billing_contact_email_addresses')
Add billing details fields to Service model and db table The fields are: Purchase order number - string field Billing contact name - text field to acommodate possible multiple contacts Billing contact email address - text field to acommodate possible multiple contacts Billing reference - string field All these fields are nullable. Notify platform admins will be able to check and edit those values in Service Settings section in Notify interface. This will help make billing tasks and reports simpler. Similar fields will also be added to Organisation model and db table.
2021-01-20 18:00:43 +00:00
# ### end Alembic commands ###
Reference in New Issue Copy Permalink