Enforce configuration of roles in Weblate
I haven't followed previous discussion about this, but there's the idea of enforcing configuration of Weblate roles (as defined in the design doc) through configuration management using Puppet.
- Anonymous users can suggest.
- Logged in users can suggest and vote on suggestions.
- Reviewers can accept suggestions.
The Puppet code created for this might need to be updated when weblate/django's API changes.
Can someone share some background on this discussion? Was it thought to protect against a specific kind of attack or bug?
#6 Updated by hefee about 1 month ago
@hefee, does this issue capture what we wrote down as "puppetize auth model"?
yes this sounds what I had in mind in regards of "puppetize auth model".
What I have in mind with puppetize is any script that is shipped via puppet and is executed regularly like a cronjob.