Mirrors/juanfont.headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2025-08-10 13:46:46 +02:00
Code Issues Projects Releases Wiki Activity

Add migration steps when policy is stored in the database

Browse Source 
Fixes: #2567
This commit is contained in:
Florian Preinstorfer 2025-05-09 19:44:15 +02:00
parent 56db4ed0f1
commit dea454b4b3
1 changed files with 23 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
CHANGELOG.md
View File

@ -64,6 +64,29 @@ new policy code passes all of our tests.
`@` should be appended at the end. For example, if your user is `john`, it
must be written as `john@` in the policy.
<details>
<summary>Migration notes when the policy is stored in the database.</summary>
This section **only** applies if the policy is stored in the database.
Headscale won't start with an invalid policy and this also means that the policy
can't be updated with the CLI. One may migrate a policy stored in the database
following these steps:
* Dump the policy to a file while still running Headscale 0.25:
`headscale policy get > policy.json`
* Create a dummy policy (here: allow all):
`echo '{"acls":[{"action":"accept","src":["*"],"dst":["*:*"]}]}' > dummy.json`
* Load the dummy policy into Headscale 0.25:
`headscale policy set --file dummy.json`
* Edit `policy.json` and migrate to policy V2
* Update to Headscale 0.26
* Load the modified policy V2:
`headscale policy set --file policy.json`
</details>
**SSH**
The SSH policy has been reworked to be more consistent with the rest of the