You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that Choria 0.28.0 is released trying to validate #2097
$ export CHORIA_SRV_DOMAIN=dev.company.net
$ choria tool config plugin.choria.srv_domain
<SNIP>
Configuration item: plugin.choria.srv_domain
║ Value: <GCP project domain, not dev.company.net>
║ URL: https://choria.io/docs/deployment/dns/
║ Data Type: string
║ Environment: CHORIA_SRV_DOMAIN
║
║ The domain to use for SRV records, defaults to the domain the
║ server FQDN is in
╙─
It looks like the lack of a default is preventing this code path from getting used. Will come up with a simple fix.
The text was updated successfully, but these errors were encountered:
treydock
added a commit
to treydock/go-choria
that referenced
this issue
Feb 8, 2024
The logic to pull config defaults from an environment variable is only used when a config has a default.
This adds empty string default for SRV domain which will trigger the logic to pull a default value also from the CHORIA_SRV_DOMAIN environment variable.
treydock
added a commit
to treydock/go-choria
that referenced
this issue
Feb 8, 2024
The logic to pull config defaults from an environment variable is only used when a config has a default.
This adds empty string default for SRV domain which will trigger the logic to pull a default value also from the CHORIA_SRV_DOMAIN environment variable.
Now that Choria 0.28.0 is released trying to validate #2097
It looks like the lack of a default is preventing this code path from getting used. Will come up with a simple fix.
The text was updated successfully, but these errors were encountered: