knife.rb and activation e-mail's link don't obey the API_FQDN on AWS

Description

(Moving to here, because I've posted on wrong repo. Source: https://github.com/chef/chef/issues/4637 )

Knife.rb and activation e-mail's link don't obey the API_FQDN on AWS. When configuring a new Chef-Server on AWS, the activation e-mail for new users and the starter kit's knife.rb uses the internal hostname from AWS machine, and don't get neither the machine hostname and the named passed on api_fqdn.

Chef Version

12.6

Platform Version

Amazon Linux 2015.09.

Replication Case

0- Configure machine and hostname and requirements.
1- Install directly from RPM, or using Chef's cookbook.
2- Configure chef-server.rb accordling the Supermarket manual and config_rb_server manual, as api configuration for Supermarket, as usual, and api_fqdn for hostnames.
3- Create a new organization and get the Starter kit. Notice that knife.rb points to wrong host
4- Create a new user, and notice that activation link stills pointing to wrong place.

Start with the chef-server.rb configuration for api_fqdn, then trace how the starter kit's knife.rb and new-user activation e-mail links are generated. Reproduce the AWS setup described in the issue and verify that both outputs use the configured API_FQDN rather than the machine's internal hostname.