Merge ~ines-almeida/launchpad:pro-enable-core18/update-models into launchpad:master
Status: | Merged |
---|---|
Approved by: | Ines Almeida |
Approved revision: | 862956bc947bf52b2c329ee1e4feb933d447721b |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~ines-almeida/launchpad:pro-enable-core18/update-models |
Merge into: | launchpad:master |
Diff against target: |
406 lines (+228/-0) 6 files modified
lib/lp/scripts/garbo.py (+32/-0) lib/lp/scripts/tests/test_garbo.py (+42/-0) lib/lp/snappy/interfaces/snap.py (+24/-0) lib/lp/snappy/model/snap.py (+44/-0) lib/lp/snappy/tests/test_snap.py (+84/-0) lib/lp/testing/factory.py (+2/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Approve | ||
Review via email: mp+453932@code.launchpad.net |
Commit message
Add new pro_enable attribute to Snap models, plus DB backfilling logic
This new bool will later determine whether a snap can use private dependencies.
Initially this attribute is NULL in the database, and will be backfilled daily, a chunk at a time. As such, we add both `_pro_enable` (the actual DB value) and `pro_enable` as a model property that determines the `pro_enable` value if one isn't set in the DB yet.
Description of the change
For more context, see: https:/
This MP adds the `pro_enable` attribute to the model, and its DB backfilling logic.
What it doesn't add:
- Browser interface to see or update this value
- Any logic changes based on this value
This should be able to be merged and start back filling the DB, even if the value isn't at all used yet.