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
main
notifications-api/migrations/versions/0339_service_billing_details.py

61 lines
1.9 KiB
Python
Raw Permalink 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
"""
reformat up to latest version of black
2024-04-01 15:12:33 -07:00
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
import sqlalchemy as sa
black, isort, flake8 Signed-off-by: Cliff Hill <Clifford.hill@gsa.gov>
2023-12-08 21:43:52 -05:00
from alembic import op
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
reformat
2023-08-29 14:54:30 -07:00
revision = "0339_service_billing_details"
down_revision = "0338_add_notes_to_service"
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
def upgrade():
# ### commands auto generated by Alembic - please adjust! ###
reformat
2023-08-29 14:54:30 -07: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)
)
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),
)
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)
)
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),
)
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 ###
def downgrade():
# ### commands auto generated by Alembic - please adjust! ###
reformat
2023-08-29 14:54:30 -07:00
op.drop_column("services_history", "purchase_order_number")
op.drop_column("services_history", "billing_reference")
op.drop_column("services_history", "billing_contact_names")
op.drop_column("services_history", "billing_contact_email_addresses")
op.drop_column("services", "purchase_order_number")
op.drop_column("services", "billing_reference")
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