-
Notifications
You must be signed in to change notification settings - Fork 29
Deploy to OpenShift command #316
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
Deploy to OpenShift command #316
Conversation
469ce40
to
9ef087e
Compare
@mohitsuman @dgolovin This is a POC for selecting a Quarkus project to deploy from the current workspace. The next step would be integrating with OpenShift Connector in order to deploy the selected Quarkus project to OpenShift. |
b9171e1
to
bf30aac
Compare
I think this should work now. I don't have access to an OpenShift cluster to test this on, though. I tried with minikube and it looks like that doesn't work. How to use:
This should also work for multi root workspaces. There should be a dialog that prompts to select which project to deploy. |
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.
After installing the latest vscode-openshift-tools CI build from https://download.jboss.org/jbosstools/adapters/snapshots/vscode-openshift-tools/?C=M;O=D, without even creating/connecting to an openshift cluster, the deploy command gives me 2 conflicting messages: @dgolovin if there's no cluster available, we want the deploy command to initiate the creation/configuration of the cluster |
15de542
to
a6ded85
Compare
I was expecting the command to reject if something goes wrong. If there is a command that returns if there is a cluster or rejects if there is none, I could use that before trying to deploy. |
@datho7561 @fbricon I generated quarkus project, it is using maven. Then I am trying to deploy and get this error: "No quarkus project detected in this folder". How do I set this folder? |
@fbricon it looks like the issue dgolovin ran into is related to jdt.ls not automatically importing the project. I'll investigate and open a bug this afternoon. @dgolovin If you open the project folder ( I'll also |
2a3d8db
to
8184429
Compare
8184429
to
e8bd39c
Compare
e8bd39c
to
afe3e25
Compare
bdad270
to
13436f9
Compare
570af11
to
0dec4fe
Compare
0dec4fe
to
d55d576
Compare
d55d576
to
b951014
Compare
b951014
to
f3c2aea
Compare
It should be openshift-tools' responsibility to perform the necessary checks for deploying to openshift (stuff involving kubectl for instance). @dgolovin please check what parts of this PR should be moved to openshift tools |
cdcb84f
to
8d2bec4
Compare
Thanks for the review, Denis! I have addressed the comments. |
4f25c20
to
ddec3cc
Compare
507fac2
to
e9861ba
Compare
e9861ba
to
72d72f0
Compare
@fbricon This should work properly with the snapshot build of OpenShift Connector 0.2.7 |
@datho7561 0.2.7 was released last week. |
Uses the existing menu to select which Quarkus project to deploy. Uses OpenShift Connector in order to deploy the Quarkus project to OpenShift. The component is created if it does not exist yet (i.e. no .odo folder is present), and it's pushed if it already exists. OpenShift Connector handles selecting/creating the application and naming the component. Closes redhat-developer#313 Signed-off-by: David Thompson <[email protected]>
72d72f0
to
8cc3dac
Compare
Hi @datho7561, for this command, do we have any changes for it to be merged ? |
@mohitsuman this PR should be good to merge. I'll merge it now. |
Uses the existing menu to select which Quarkus project to deploy.
Uses OpenShift Connector in order to deploy the Quarkus project to
OpenShift.
OpenShift Connector handles selecting/creating the application and
naming the component.
Closes #313
Signed-off-by: David Thompson [email protected]