starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[PR #1647] [MERGED] implement selfupdate and pass expiry #2233

New Issue
Closed
opened 2025-12-29 03:20:19 +01:00 by adam · 0 comments
adam commented 2025-12-29 03:20:19 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/1647
Author: @kradalby
Created: 12/10/2023
Status: ✅ Merged
Merged: 1/5/2024
Merged by: @kradalby

Base: main ← Head: propogate-expiry

📝 Commits (4)

  • 71e158e implement selfupdate mechanism
  • 623c6aa Fix and test node expiry
  • 8cb4989 make 1.36 the last supported version
  • a77a229 print run, remove erros from test runner script

📊 Changes

11 files changed (+114 additions, -52 deletions)

View changed files

📝 CHANGELOG.md (+1 -1)
📝 hscontrol/db/node.go (+34 -8)
📝 hscontrol/mapper/mapper.go (+2 -13)
📝 hscontrol/notifier/notifier.go (+15 -0)
📝 hscontrol/poll.go (+8 -0)
📝 hscontrol/poll_noise.go (+1 -1)
📝 hscontrol/types/common.go (+10 -0)
📝 integration/general_test.go (+25 -13)
📝 integration/run.sh (+4 -2)
📝 integration/scenario.go (+13 -13)
📝 integration/scenario_test.go (+1 -1)

📄 Description

Currently we support informing nodes upon change, but do not have a mechanism for updating the node from control and down.

This commits add a SelfUpdate state change and it is used to inform a node if it keys has been expired control side.

This PR makes 1.36 the last supported version as it exposes keyexpiry information.

fixes #1645

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/juanfont/headscale/pull/1647 **Author:** [@kradalby](https://github.com/kradalby) **Created:** 12/10/2023 **Status:** ✅ Merged **Merged:** 1/5/2024 **Merged by:** [@kradalby](https://github.com/kradalby) **Base:** `main` ← **Head:** `propogate-expiry` --- ### 📝 Commits (4) - [`71e158e`](https://github.com/juanfont/headscale/commit/71e158eb791ab27d7b127f33fbed1252c49341ba) implement selfupdate mechanism - [`623c6aa`](https://github.com/juanfont/headscale/commit/623c6aa2c288f1adf8a32819329b1792d92be500) Fix and test node expiry - [`8cb4989`](https://github.com/juanfont/headscale/commit/8cb498966bd91ccb74dd964c3db7cdaaeee6b01d) make 1.36 the last supported version - [`a77a229`](https://github.com/juanfont/headscale/commit/a77a2290534e942ae10427fd3bee5779381bc98f) print run, remove erros from test runner script ### 📊 Changes **11 files changed** (+114 additions, -52 deletions) <details> <summary>View changed files</summary> 📝 `CHANGELOG.md` (+1 -1) 📝 `hscontrol/db/node.go` (+34 -8) 📝 `hscontrol/mapper/mapper.go` (+2 -13) 📝 `hscontrol/notifier/notifier.go` (+15 -0) 📝 `hscontrol/poll.go` (+8 -0) 📝 `hscontrol/poll_noise.go` (+1 -1) 📝 `hscontrol/types/common.go` (+10 -0) 📝 `integration/general_test.go` (+25 -13) 📝 `integration/run.sh` (+4 -2) 📝 `integration/scenario.go` (+13 -13) 📝 `integration/scenario_test.go` (+1 -1) </details> ### 📄 Description Currently we support informing nodes upon change, but do not have a mechanism for updating the node from control and down. This commits add a SelfUpdate state change and it is used to inform a node if it keys has been expired control side. This PR makes 1.36 the last supported version as it exposes keyexpiry information. fixes #1645 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 03:20:19 +01:00
adam closed this issue 2025-12-29 03:20:19 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#2233
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?