-
Notifications
You must be signed in to change notification settings - Fork 61
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
Bug Fixes + Support for External Load Balancer #95
Conversation
shailesh91
commented
Sep 6, 2018
•
edited
Loading
edited
- Get FQDN resolves Ip into standard PTR format, it should have resolved either to machine name or just returned an IP. (https://en.wikipedia.org/wiki/Reverse_DNS_lookup#IPv4_reverse_resolution)
- Portal Unregister resource encoding fixed to UTF8
- Server Upgrade Configuration, Windows Service Resource wasn't imported and one of the conditions failed due to type mismatch
- Deprecating Global SSL Certs. Making Node Level Certificates the Standard.
- Multiple SSL certs per machine with a target component (can specify multiple targets for the same certificate)
- Dividing Configure DSC Configuration file into Configure components, Federation and Registering SQL Server.
- Fixing the endpoint URLs output at end of the job
- Adding support for External Load Balancers
1. Get FQDN resolves Ip into standard PTR format, it should have resolved either to machine name or just returned an ip. (https://en.wikipedia.org/wiki/Reverse_DNS_lookup#IPv4_reverse_resolution) 2. Portal Unregister resource encoding fixed to UTF8 3. Server Upgrade Configuration, Windows Service Resource wasn't imported and one of the conditions failed due type mismatch
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.
@shailesh91 thanks for all this nice fixes. I like the new Default certificate handling.
About federation. I would prefer, to "hide" the Server Port on federation URL if it is 443 as it gives nicer URLs for the Services on this machine. It has to be considered in "ArcGISFederation Federate".
@spitzerr I will consider making the necessary changes to the federation resource. |