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.

Sign up for GitHub

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

Jump to bottom

Filtering devfile stacks based on the architecture field in metadata #6669

Open
2 of 3 tasks
kadel opened this issue Mar 20, 2023 · 2 comments
Open
2 of 3 tasks

Filtering devfile stacks based on the architecture field in metadata #6669

kadel opened this issue Mar 20, 2023 · 2 comments
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).

Comments

@kadel
Copy link
Member

kadel commented Mar 20, 2023 •
edited by rm3l
Loading

User Story

  • As an odo user using a cluster running on IBM Z
  • So that I don't create a component that uses devfile that won't work on my cluster.

Associated user stories:

/kind user-story
/priority high
@openshift-ci openshift-ci bot added kind/user-story An issue of user-story kind priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). labels Mar 20, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Mar 20, 2023
@valaparthvi valaparthvi removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Apr 20, 2023
@valaparthvi
Copy link
Contributor

valaparthvi commented Apr 20, 2023 •
edited
Loading

Grooming Call [April 20 '23]:

  1. odo registry list output to architectures
  2. odo registry --filter to be extend to filter based on archs.

This was referenced May 9, 2023
Closed
Closed
Open
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 31, 2023
@rm3l rm3l added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
odo Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kadel @rm3l @valaparthvi