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

[Feature] Please add a "column" "notes" to your objects. #1156

New Issue
Open
opened 2025-12-29 02:28:36 +01:00 by adam · 1 comment
adam commented 2025-12-29 02:28:36 +01:00
Owner
Copy Link

Originally created by @noseshimself on GitHub (Nov 21, 2025).

Use case

"We failed. We failed miserably."

Please bear with me and my writing; I had an overdose of sarcaustic acid in my coffee this week.

I'm helping (you can't call it consulting; this is first aid) a client who moved his Cisco-based VPN nightmare to... Headscale (because, you know, Tailscale is too expensive and not in our hands so the Head of IT did the decapitated chicken thing and set up "their own" mesh based on Tailscale, managed by a contractor -- very own). They have been in the process of integrating the administration of about 800 mesh users and an appropriate number of nodes into their "IT resource management system" for about 18 months now but the only thing so far are a few comments in otherwise empty .py files which in my eyes is very little integration even though it compiles.

The simplest immediate tool they could use was adding a comment referring to tickets that refer to administrative changes on objects (creation, changing tags, that kind of stuff) and maybe even leave a short note if that is really required.

Please add a parameter to headscale apikeys, preauthkeys, nodes and users that can be set and retrieved using the CLI (and maybe using headscale-admin). If the simple solution only permits (over)writing the note and reading it that would be more than enough.

Description

Add "fields" to your "object database" for nodes, users, apikeys and preauthkeys for storage of arbitrary data blobs. Add a simple access method to the CLI for inserting and retrieving/displaying the contents. Add a marker to the * list command to remind users that there is additional data available.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

No response

Originally created by @noseshimself on GitHub (Nov 21, 2025). ### Use case "We failed. We failed miserably." Please bear with me and my writing; I had an overdose of sarcaustic acid in my coffee this week. I'm helping (you can't call it consulting; this is first aid) a client who moved his Cisco-based VPN nightmare to... Headscale (because, you know, Tailscale is too expensive and not in our hands so the Head of IT did the decapitated chicken thing and set up "their own" mesh based on Tailscale, managed by a contractor -- very own). They have been in the process of integrating the administration of about 800 mesh users and an appropriate number of nodes into their "IT resource management system" for about 18 months now but the only thing so far are a few comments in otherwise empty .py files which in my eyes is very little integration even though it compiles. The simplest immediate tool they could use was adding a comment referring to tickets that refer to administrative changes on objects (creation, changing tags, that kind of stuff) and maybe even leave a short note if that is really required. Please add a parameter to headscale apikeys, preauthkeys, nodes and users that can be set and retrieved using the CLI (and maybe using headscale-admin). If the simple solution only permits (over)writing the note and reading it that would be more than enough. ### Description Add "fields" to your "object database" for nodes, users, apikeys and preauthkeys for storage of arbitrary data blobs. Add a simple access method to the CLI for inserting and retrieving/displaying the contents. Add a marker to the * list command to remind users that there is additional data available. ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? _No response_
adam added the enhancement label 2025-12-29 02:28:36 +01:00
adam commented 2025-12-29 02:28:36 +01:00
Author
Owner
Copy Link

@ArcticLampyrid commented on GitHub (Nov 30, 2025):

I think the most suitable approach is to create your own dashboard and record all changes.
It seems beyond the scope of this project.

@ArcticLampyrid commented on GitHub (Nov 30, 2025): I think the most suitable approach is to create your own dashboard and record all changes. It seems beyond the scope of this project.
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 enhancement
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#1156
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?