Skip to content

group and give description for gitpod ports #9285

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

Closed
konne opened this issue Apr 13, 2022 · 8 comments
Closed

group and give description for gitpod ports #9285

konne opened this issue Apr 13, 2022 · 8 comments

Comments

@konne
Copy link

konne commented Apr 13, 2022

the current port list just contains all currently shared ports.

This is very confusing because we open for example a lot of nodejs debugging ports that are not needed to be used by the users.
It would be great to first have a possibility in the gitpod.yml to give a group name

ports:
  - port: 33000-33999
     group: debugging
     state: closed
     onOpen: ignore
   - port: 80-2000
     group: web
     state: opened
   - port: 6008
     group: VNC
     state: closed

On Top it would be even great to give each port also a description that would be visible beside the port number like

ports:

  • port: 33000-33999
    ...

  • port 330100

    • description: Debug API gateway
  • port 330101

    • description: Debug Service1
  • port 6008

    • description: VNC
@loujaybee
Copy link
Member

There is another use case for this: In some cases, frameworks, or even integrations with Gitpod open ports for their own use, however, it's not always explicit where this port came from/why it's been opened. Having descriptions and encouraging explicit naming or descriptions of ports could make it more clear when there's an unknown / undefined opened port, possibly by grouping or labeling these ports as unknown. We could also take a look at guessing what the port might be related to by inspecting the parent process.

@akosyakov
Copy link
Member

akosyakov commented May 26, 2022

@konne It actually supported:
Screenshot 2022-05-26 at 09 09 29

But we are missing docs about it, sorry.

@konne
Copy link
Author

konne commented May 26, 2022

@akosyakov thx & cool. I will asap add it to our config.

@akosyakov
Copy link
Member

I'm closing it, please reopen if it does not work.

For auto derived name and description: #3374

@konne
Copy link
Author

konne commented May 26, 2022

@akosyakov do you also plan to implement grouping.

  • server
    • 80
    • 8080
  • debugging
    • 5061
    • 5062
    • 5062,..
      This was also part of the idea / feature request.

@konne
Copy link
Author

konne commented May 26, 2022

@akosyakov names and descriptions are working

@akosyakov
Copy link
Member

Should it work based on name attribute or you think there should be another attribute? Would you file another issue just about grouping? 🙏

@konne
Copy link
Author

konne commented May 27, 2022

@akosyakov can you please add this ticket to the epic, thanks

#10294

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants