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
The plugin pulls the domains from the org, not the wic app. I suspect this is done because the user in question likely does not have permissions to access the wic app, and you, being the genial sort like to save me keystrokes. Unfortunately, when determining base url incorrectly we throw off the route flag (as whatever populates the cli models appears to prefer private domains before shared domains (wild guess)), and thus we end up assuming that the url for WIC is the 0th domain in my current org, which is not the apps domain.
I propose that route requires a fqdn.
Here's how it looks.
➜ cf_will_it_connect_plugin git:(master) cf willitconnect --route=willitconnect-dysteleological-laburnum --host=amazon.com --port=80
[Host: amazon.com - Port: 80 - WillItConnect: https://willitconnect-dysteleological-laburnum.joshq.cfapps.io/v2/willitconnect]
[Unable to access willitconnect: Post https://willitconnect-dysteleological-laburnum.joshq.cfapps.io/v2/willitconnect: x509: certificate is valid for *.cfapps.io, cfapps.io, not willitconnect-dysteleological-laburnum.joshq.cfapps.io]
➜ cf_will_it_connect_plugin git:(master) cf willitconnect --route=willitconnect-dysteleological-laburnum --host=amazon.com --port=80
The text was updated successfully, but these errors were encountered:
krujos
added a commit
to krujos/cf_will_it_connect_plugin
that referenced
this issue
Oct 17, 2016
The plugin pulls the domains from the org, not the wic app. I suspect this is done because the user in question likely does not have permissions to access the wic app, and you, being the genial sort like to save me keystrokes. Unfortunately, when determining base url incorrectly we throw off the
route
flag (as whatever populates the cli models appears to prefer private domains before shared domains (wild guess)), and thus we end up assuming that the url for WIC is the 0th domain in my current org, which is not the apps domain.I propose that route requires a fqdn.
Here's how it looks.
The text was updated successfully, but these errors were encountered: