Support writing to pihole.toml directly

DL6ER · June 25, 2024, 12:35pm

Since there was no further discussion here, I merged the already approved PR to development-v6.

github.com/pi-hole/FTL

Add read-only config option

pi-hole:development-v6 ← pi-hole:new/misc_readOnly

opened 07:17PM - 02 Jun 24 UTC

DL6ER

+69 -1

# What does this implement/fix? Add new `misc.readOnly` config option to forc…e the configuration to be read-only. It can only be modified through the config file but neither the API nor the CLI as long as read-only mode is enabled. **Related issue or feature (if applicable):** https://discourse.pi-hole.net/t/support-writing-to-pihole-toml-directly/70522/ **Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A --- **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 2. I have commented my proposed changes within the code. 3. I am willing to help maintain this change if there are issues with it later. 4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) ## Checklist: - [x] The code change is tested and works locally. - [x] I based my code and PRs against the repositories `developmental` branch. - [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions - [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship - [x] I have read the above and my PR is ready for review.

@Javex please make sure to get back onto development-v6 to ensure you receive future updates, the feature branch will not receive any further updates.