Skip to content
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.

Need a better way of enabling CodeReady Workspaces #161

Open
ralanlittle opened this issue Apr 24, 2020 · 1 comment
Open

Need a better way of enabling CodeReady Workspaces #161

ralanlittle opened this issue Apr 24, 2020 · 1 comment
Assignees

Comments

@ralanlittle
Copy link
Contributor

ralanlittle commented Apr 24, 2020

We need a method from the Kabanero console to active the CodeReady Workspace. Currently the CodeReady workspace is only shown on the console if CRW is active. And the method of activating it is to navigate to the Kabanero operator, find its YAML update the codereadywork space value from false to true.

What I would expect is to always have the card on the Kabanero console. And the button would have an install option until it is up running, when the current button would be used. Under the covers I would expect the UI to issue an activate CRW event. The event handler would extract the Kabanero YAML, update the value, and Kubectl Apply the update. The event handler would go into a loop throwing events to check the status until it was successful in which case it would throw a CRW available event, or upon failure or timeout it would throw a CRW Failed event which would log error for Todd. The UI when it received the event would change from its pending state to call state.

@alohr51
Copy link
Member

alohr51 commented Apr 24, 2020

A PR went in yesterday to update the codeready workspace value on the CRD. This is only helpful if you already have a kabanero instance available and want to enable/disable codeready. You can see the design screenshot of this in this comment

We need some more work to make that happen if no kabanero instance is created yet as of right now the feature only lets you update an existing kabanero instance, not create one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants