Config Protection

[0x4007]

Not sure if this is fully possible from within the webhook event, but the idea is that only admins or billing managers should be able to modify the config because it affects money flow.

On commit, check if config was modified. If it is unauthorized, rollback the change by immediately committing the previous version as the UbiquiBot.

This should make it near impossible for fraud.

---

Seems like relevant logic I saw in a pull.

[0x4007]

@Keyrxng this might be easy for you given the similar logic.

[Keyrxng]

This should be a standalone plugin? or should I include it in assistive-pricing?

[gentlementlegen]

The idea is that we want to limit who can access the configuration file, and also avoid having someone overriding it per repo basis (because even though you don't have access to the organization configuration you can always put yours in some repo where you have control) so I'd say it would be a plugin. We were discussing about having protection on branches as well if that was a solution.

[Keyrxng]

Understood, I have a couple of good ideas for it

P.S it was mentioned previously about enforcing tests, I think we should enforce them. Any new plugins should have a test suite which covers at least the basics then any new features should extend those. No set limits or anything just follow the same test structure as other plugins

[gentlementlegen]

We have tests in the template for plugins as well (and I usually don't merge PRs that do not link QA and tests). Feel free to improve the template with new tests if you feel it is required. And let's be careful during reviews as well.