Bug #16881
Puppetize critical Weblate configuration
Start date:
Due date:
% Done:
0%
Description
Great parts of our setup were implemented so far by clicking stuff in the admin web UI, which:
- Makes it hard to audit & review both the current state of things and future changes.
- Implies we have no way to set up another, identical instance of this platform, which is problematic:
- It’s hard to replicate the setup locally for dev/test purposes.
- If we ever screw up the database hopelessly, we can’t easily reset it and restore the settings we really want to keep.
So it would be nice to encode in Puppet the settings we really care about, such as ACLs for groups, that implement critical parts of our security model (Bug #16855).
Subtasks
Related issues
|
Related to Tails - |
Resolved | ||
| Blocked by Tails - Bug #17338: Enforce configuration of roles in Weblate | Needs Validation |
History
#1 Updated by intrigeri 2019-07-15 13:37:03
- related to
Bug #16855: Enforce reviewer policy on Weblate added
#2 Updated by intrigeri 2019-09-12 09:18:37
This would be really really nice but I don’t think we can reasonably treat is as a blocker for the completion of the SponsorL follow-up project.
#3 Updated by intrigeri 2019-09-13 09:45:07
- Priority changed from Normal to Elevated
#4 Updated by hefee 2019-12-16 18:00:15
- blocked by Bug #17338: Enforce configuration of roles in Weblate added