Pivotal Cloud Foundry© 1.9.x, 1.10.x, 1.11.x
The command cf share-private-domain <org> <domain> is used to share a domain with another org but it does not display properly in Apps Manager when viewed under the other org.
Also, attempting to add a route through Apps Manager using the organization with which the domain was shared results in an incorrectly added route.
The following steps will result in this problem:
1. Private domain was created under OrgA
2. Private domain was shared with OrgB (cf share-private-domain ORG DOMAIN)
3. Private domain does not display under OrgB -> problem #1
4. Route is mapped to a shared domain under OrgB but instead ends up getting routed to the shared private domain. The added route is not the one selected from drop-down list.-> problem #2
This is caused by a code defect in Apps Manager.
There are 2 defects related to share-private-domains with Apps Manager:
- Problem #1 A user should be able to see shared private domains in the domains tab
- Problem #2 Apps Manager maps a route other than the one selected in the drop-down list (for an app route)
The first issue of not displaying shared domains affects 1.9, 1.10, and 1.11. It is fixed in the 1.9.38, 1.10.25 and 1.11.11 releases of Elastic Runtime.
The second issue of mapping to the wrong route affects 1.9 and 1.10. Newer versions (1.11+) do not have this issue. It is resolved in 1.9.38 and 1.10.25.
It is also possible to workaround this issue by using the cf CLI for operations related to shared private domains. The cf CLI will not have problems with shared private domains as this is a defect in Apps Manager and not cf CLI or cloud controller.