Skip to content
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

Adopt devfile format for Stacks #12924

Closed
6 tasks done
slemeur opened this issue Mar 19, 2019 · 1 comment
Closed
6 tasks done

Adopt devfile format for Stacks #12924

slemeur opened this issue Mar 19, 2019 · 1 comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. severity/P1 Has a major impact to usage or development of the system.

Comments

@slemeur
Copy link
Contributor

slemeur commented Mar 19, 2019

Description

A stack is a workspace template, providing ready to use developer stack for a particular technology.
That concept will remain in Che 7, but will need to be adapted to the devfile.

The goal is that we don't want to rely anymore on workspace json, we don't want to display that to end-user.

Today, the way the stacks are getting configured is not easy to manage. If someone wants to provide a different set of stacks, it needs a complete new assembly. We should be improving this.

As we are going to introduce a registry of plugin - we should be thinking about providing the stacks as a registry of specific devfile too.

User Stories

Stacks Registry

As we are going to introduce a registry of plugin - we should be looking at providing the stacks as a registry of specific devfile too.

  • As an admin of Eclipse Che, at installation/deployment I should be able to configure the repository that is used to provide the list of stacks.
  • As an admin of Eclipse Che, I should be possible to change the list of stacks and replace it by pulling a different repository
  • As an admin of Eclipse Che, I should be able to extend the list of stacks with another repository, in the case I want to provide the upstream stacks + a list of stacks that I'm going to manage myself.

Stacks for End-User

  • As a developer, I can see the list of stacks and when I look at the configuration of the stack, I can see it is defined with a devfile
  • As a developer, I can use a stack (define as a devfile) to create a workspace
  • As a developer, I can register new stack by providing a devfile with a set of other meta-information. That stacks will be available only to me.

Implementation

@slemeur
Copy link
Contributor Author

slemeur commented Oct 9, 2019

closing as everything has been handle

@slemeur slemeur closed this as completed Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants