Skip to content

V0.26 Route List formatting #2612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 of 4 tasks
craig4who opened this issue May 18, 2025 · 11 comments
Open
2 of 4 tasks

V0.26 Route List formatting #2612

craig4who opened this issue May 18, 2025 · 11 comments
Labels
bug Something isn't working
Milestone

Comments

@craig4who
Copy link

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When running the command

headscale nodes list-routes

If you have lots of routes the formatting of the display is hard to read and understand, making it impossible to know what’s in the DB.

Expected Behavior

When running the command as previously done with 0.25.1 when listing the routes you can easily see what routes are pending in order to load them into the DB.

Steps To Reproduce

Tried running with column t at the end it looks a little bit better but not 100%

Environment

- OS: Ubuntu 22.04.5 LTS
- Headscale version: 0.26
- Tailscale version: latest

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Debug information

NA

@craig4who craig4who added the bug Something isn't working label May 18, 2025
@hanjo
Copy link

hanjo commented May 19, 2025

maybe it helps to pipe to | less -S ?

@craig4who
Copy link
Author

No that didnt help :-( Have you got the version installed and tried it? Do you know what i mean?

@kradalby
Copy link
Collaborator

It won't return to the old format, but maybe it could wrap/fold inside each column

@craig4who
Copy link
Author

Are you getting the same thing? Can you see what i mean?

@kradalby
Copy link
Collaborator

I dont have a lot of routes, it would be helpful with a few screenshots

@craig4who
Copy link
Author

Let me know if you need anymore. I personally rolled back but i can upgrade again.

@kradalby kradalby added this to the v0.27.0 milestone May 21, 2025
@craig4who
Copy link
Author

Image

@craig4who
Copy link
Author

@kradalby Hope that helps you.

@craig4who
Copy link
Author

@hanjo This is with your suggestion

Image

@craig4who
Copy link
Author

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants