-
Notifications
You must be signed in to change notification settings - Fork 13
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
Implement --domain option #63
Conversation
This is related to voxpupuli/beaker-hostgenerator#261 (comment). This now adds a bunch of |
ed4768e
to
7662bfb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at this I'm wondering if we should make domain
an Optional[String]
and drop use_fqdn
. This could map nicely to where we specify the domain as an option to beaker-hostgenerator and stop overriding the hostname.
For compatibility I'd say that it should append domain
if it's set, otherwise fall back to use_fqdn
. So roughly
def os_release_to_setfile(os, release, use_fqdn: false, pidfile_workaround: false, domain: nil)
domain ||= 'example.com' if use_fqdn
options = {}
options[:hostname] = "#{name}.#{domain}" if domain
end
okay it was clearly too early when I wrote that code. |
59500f6
to
93d260c
Compare
@ekohl I implemented your suggestion |
97772d4
to
76da92f
Compare
2be03fc
to
3f12367
Compare
Previously, the domain `example.com` was hardcoded for the beaker instances. This is now configureable.
@ekohl, this looks good to me. Are you fine with merging it? |
Previously, the domain
example.com
was hardcoded for the beaker instances. This is now configureable.