Add sys.hostname configuration for supervisor

[jsirex]

Like for sys.ip it will be nice to have possibility to advertise servers' hostname.

Usually I have "internal name" for server, like internal-server-01.local.domain.
However, I can assign additional DNS(-es) to it, like public.name.official.domain.

I want to use binding and service discovery. But if I use TLS/SSL encryption I must use "correct" name. But bind.backend.first.sys.hostname will resolve to the local domain name, so I will end up with "common name mismatch".

Current workaround is to hardcode connection names.

[christophermaier]

The hostname would end up being something like internal-server-01 or public, given your examples above.

From your description, it sounds like having access to a particular fully-qualified domain name might work better for you (e.g., adding an option like hab sup run --fqdn=public.name.official.domain)... is that accurate?

[jsirex]

Yep. fqdn options is good here.

I'm also thinking about an general approach to catch all future use-cases if any..
For example, introduce general options for the sys data.
Run with: hab sup run --system-info fqdn=f.q.d.n --system-info foo-bar=baz --system-info tag=az1
Use with template:

tag = {{bind.backend.sys.tag }}
conn = {{bind.backend.sys.fqdn}}
text = {{bind.backend.sys.foo-bar}}

[christophermaier]

We can likely add fqdn without much issue.

More general metadata would be interesting, and there is some prior art in the event stream feature, but it might take a bit of thinking to sort out the best way forward. Would you mind creating a separate issue for just that?

Thanks! 🙇

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.