[
https://issues.jboss.org/browse/JBIDE-10133?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10133:
------------------------------------------
I'll reproduce the -Dlibra_server usecase to see why this actually fails.
Since you cannot spot the config files, and the wizard still worked, it fell back to the
built in default which uses
openshift.redhat.com as libra_server.
I'm not completely sure by heart at which point the openshift CLI commands create
those files. But to me there's little use to create those by hand. Why not just
installing the CLI tools and do some manipulations until you get the files? The CLI tools
would also allow you to verify what the wizard tells you (domain name, applications etc.)
OpenShift URL should be looked up in the configuration files that the
CLI uses (so we can easily switch to staging environment)
-------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10133
URL:
https://issues.jboss.org/browse/JBIDE-10133
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.M4
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M5
There's currently no easy way for a (power-) user to switch to the staging
environment since the PaaS URL is inidicated in the code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira