migrations/versions/0261_service_volumes.py

"""

Revision ID: 0261_service_volumes
Revises: 0260_remove_dvla_organisation
Create Date: 2019-02-13 13:45:00.782500

"""

from itertools import product

import sqlalchemy as sa
from alembic import op

revision = "0261_service_volumes"
down_revision = "0260_remove_dvla_organisation"


TABLES = ["services", "services_history"]
CHANNELS = ["volume_email", "volume_letter", "volume_sms"]


def upgrade():
    for table in TABLES:
        op.add_column(
            table,
            sa.Column(
                "consent_to_research",
                sa.Boolean(),
                nullable=False,
                server_default=sa.false(),
            ),
        )
        for channel in CHANNELS:
            op.add_column(table, sa.Column(channel, sa.Integer(), nullable=True))


def downgrade():
    for table in TABLES:
        op.drop_column(table, "consent_to_research")
        for channel in CHANNELS:
            op.drop_column(table, channel)
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete. 2019-02-13 14:00:52 +00:00			`"""`

Bump migration version 2019-02-15 10:09:44 +00:00			`Revision ID: 0261_service_volumes`
			`Revises: 0260_remove_dvla_organisation`
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete. 2019-02-13 14:00:52 +00:00			`Create Date: 2019-02-13 13:45:00.782500`

			`"""`
reformat up to latest version of black 2024-04-01 15:12:33 -07:00
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete. 2019-02-13 14:00:52 +00:00			`from itertools import product`

black, isort, flake8 Signed-off-by: Cliff Hill <Clifford.hill@gsa.gov> 2023-12-08 21:43:52 -05:00			`import sqlalchemy as sa`
			`from alembic import op`
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete. 2019-02-13 14:00:52 +00:00
reformat 2023-08-29 14:54:30 -07:00			`revision = "0261_service_volumes"`
			`down_revision = "0260_remove_dvla_organisation"`
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete. 2019-02-13 14:00:52 +00:00

reformat 2023-08-29 14:54:30 -07:00			`TABLES = ["services", "services_history"]`
			`CHANNELS = ["volume_email", "volume_letter", "volume_sms"]`

Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete. 2019-02-13 14:00:52 +00:00
			`def upgrade():`
Also store consent to research against a service It makes most sense to collect this at the same time as the estimated volumes. Which means we need to store it somewhere; we can’t put it straight into the ticket. 2019-02-14 23:57:08 +00:00			`for table in TABLES:`
reformat 2023-08-29 14:54:30 -07:00			`op.add_column(`
			`table,`
			`sa.Column(`
			`"consent_to_research",`
			`sa.Boolean(),`
			`nullable=False,`
			`server_default=sa.false(),`
			`),`
			`)`
Also store consent to research against a service It makes most sense to collect this at the same time as the estimated volumes. Which means we need to store it somewhere; we can’t put it straight into the ticket. 2019-02-14 23:57:08 +00:00			`for channel in CHANNELS:`
			`op.add_column(table, sa.Column(channel, sa.Integer(), nullable=True))`
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete. 2019-02-13 14:00:52 +00:00

			`def downgrade():`
Also store consent to research against a service It makes most sense to collect this at the same time as the estimated volumes. Which means we need to store it somewhere; we can’t put it straight into the ticket. 2019-02-14 23:57:08 +00:00			`for table in TABLES:`
reformat 2023-08-29 14:54:30 -07:00			`op.drop_column(table, "consent_to_research")`
Also store consent to research against a service It makes most sense to collect this at the same time as the estimated volumes. Which means we need to store it somewhere; we can’t put it straight into the ticket. 2019-02-14 23:57:08 +00:00			`for channel in CHANNELS:`
			`op.drop_column(table, channel)`