Merge ~ines-almeida/launchpad:cleanup-after-pro-enable-migration into launchpad:master
Status: | Merged |
---|---|
Approved by: | Ines Almeida |
Approved revision: | f64689d3c062f3aabf5fb460fc6a970d6c62034c |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~ines-almeida/launchpad:cleanup-after-pro-enable-migration |
Merge into: | launchpad:master |
Diff against target: |
351 lines (+3/-218) 5 files modified
lib/lp/scripts/garbo.py (+0/-32) lib/lp/scripts/tests/test_garbo.py (+0/-42) lib/lp/snappy/interfaces/snap.py (+0/-11) lib/lp/snappy/model/snap.py (+3/-58) lib/lp/snappy/tests/test_snap.py (+0/-75) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jürgen Gmach | Approve | ||
Review via email: mp+466137@code.launchpad.net |
Commit message
Cleanup after snap.pro_enable migration
The migration has finishied months ago. This removes the garbo jobs and the auxiliary code that was added to aid the migration.
We also set the 'pro_enable' attribute as non-null now that there are no longer any null values in our databases.
Description of the change
All tests in `snappy.tests` have run successfully.
This is related to this DB MP: https:/
And to this Jira ticket: https:/
I will request for the following query to be run in production before merging this MP, for a last sanity check:
`SELECT pro_enable, Count(*) FROM Snap GROUP BY pro_enable;`
This query returned no null values in December 8th 2023.