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
{{ message }}
This repository has been archived by the owner on Nov 29, 2017. It is now read-only.
Thought that was fixed. The two domains currently must be the same. No idea why we have the two. Loggregator uses the system_domain and then goes and shares the value with the CLI user. Remove the .com
properties:
...snip...
domain: <%= dns %>
system_domain: <%= dns %>.com
I think this is an error; at least it breaks my deployment to *.co.uk.
Specifically, my loggregator tries to register itself to "uris":["loggregator.mydomain.co.uk.com"]
when it should register to "uris":["loggregator.mydomain.co.uk"]
Reply to this email directly or view it on GitHub: #267
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
templates/v149/aws/medium/deployment_file.yml.erb#L162
hardcodes the system_domain to end in .comI think this is an error; at least it breaks my deployment to
*.co.uk
.Specifically, my loggregator tries to register itself to
"uris":["loggregator.mydomain.co.uk.com"]
when it should register to
"uris":["loggregator.mydomain.co.uk"]
The text was updated successfully, but these errors were encountered: