If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Deploy Splice 1.1.30 to Stage

RESOLVED FIXED

Status

Content Services Graveyard
Tiles: Ops
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: tspurway, Assigned: relud)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
We had a bug in our data copying script, which didn't reset the ID sequences properly.  This has been fixed in 1.1.30.

To deploy, we should:

* drop existing RDS campaign instance
* drop the alembic_version table in Redshift
* run `SPLICE_IGNORE_REDSHIFT=true manage.py db upgrade`
* run the rs_to_pg.py script
* test deploying a past distribution
(Assignee)

Updated

2 years ago
Assignee: nobody → dthornton
Status: NEW → ASSIGNED
(Assignee)

Comment 1

2 years ago
This works, but:

Also creates the alembic_version table in redshift.

Probably doesn't matter, but worth mentioning: throughout the code `if 'SPLICE_IGNORE_REDSHIFT' in os.environ` is used, which means that SPLICE_IGNORE_REDSHIFT=false would do the wrong thing.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED

Comment 2

2 years ago
Hey Daniel,

Thanks for the updates.

Yes, alembic always creates "alembic_version" for version control. Can't ignore this one.
The "SPLICE_IGNORE_REDSHIFT" was initially used as a flag, doesn't matter what value it is. Will fix it, make it explicit.

Can I use staging Splice to do some tests now? Wonder how much faster the traffic is now.

Thanks,
(Assignee)

Comment 3

2 years ago
yep, go ahead and test away
You need to log in before you can comment on or make changes to this bug.