Open fbricon opened 3 years ago
createFromRootWorkspaceFolder
call triggers extension activation anything can happen:We can address 3, 4 and 5 by asking to login, provide project name and application name. That would keep workflow going.
For 1 and 2 we can initiate create/configuration of the cluster, but then folder deployment should be restarted manually.
@fbricon WDYT?
but then folder deployment should be restarted manually.
why? What prevents you from storing the request?
and what if we preset project name and application name with the project's artifactId? leaving a chance to the user to overwrite it?
but then folder deployment should be restarted manually.
why? What prevents you from storing the request?
Most likely it can be done. But considering time spend for starting CRC and then logging in to the cluster, request to enter application name would look a little unexpected and disconnected from original attempt to create component. I would be confused.
and what if we preset project name and application name with the project's artifactId? leaving a chance to the user to overwrite it?
That is something to check with odo team tomorrow during sync call. There was a discussion about that, but I am not sure if it was implemented.
@dgolovin Let's discuss this in context of the latest workflow.
If there's no cluster available, we want vscode-quarkus' "Deploy to Openshift" command to initiate the creation/configuration of the cluster. See https://github.com/redhat-developer/vscode-quarkus/pull/316#issuecomment-726870993
Maybe "openshift.component.createFromRootWorkspaceFolder" is not suited for what we're trying to do, we might need a different command.