Skip to content

Devfile Registry editor is to allow devfile version selection and use when creating a component #4189

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

Closed
vrubezhny opened this issue Jun 7, 2024 · 0 comments · Fixed by #4467
Assignees
Milestone

Comments

@vrubezhny
Copy link
Contributor

A Devfile Registry may provide a set of different versions for the same devfile:

 NAME                          REGISTRY                DESCRIPTION                                  ARCHITECTURES          VERSIONS                                                                    
 go                            DefaultDevfileRegistry  Go is an open source programming languag...                         1.0.2, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.3.1, 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0                         

However, we do not allow users to select the version of the devfile to use when creating the component, always using the default one:
image

IMHO, it would be good to allow users to select a devfile version to use from the list of available versions when creating a component.

@vrubezhny vrubezhny self-assigned this Jun 12, 2024
@rgrunber rgrunber moved this to 🏗 In progress in IDE Cloudaptors Jun 18, 2024
@vrubezhny vrubezhny moved this to ✍ In Progress in IDE Cloudaptors Aug 28, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 13, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 13, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 14, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 14, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 14, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 14, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 14, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 14, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 15, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 20, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 20, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 20, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 20, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 23, 2024
@vrubezhny vrubezhny moved this from 📝 In Progress to 👀 In review in IDE Cloudaptors Sep 23, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 24, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 24, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Oct 4, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Oct 7, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Oct 7, 2024
vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Oct 7, 2024
datho7561 pushed a commit that referenced this issue Oct 7, 2024
… when creating a component #4189

Fixes: #4189
Issue: #3850

Signed-off-by: Victor Rubezhny <[email protected]>
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in IDE Cloudaptors Oct 7, 2024
@vrubezhny vrubezhny added this to the 1.17.0 milestone Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
1 participant