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

Pass a list of architectures to support to Alizer #6805

Open
Tracked by #6669
feloy opened this issue May 9, 2023 · 8 comments
Open
Tracked by #6669

Pass a list of architectures to support to Alizer #6805

feloy opened this issue May 9, 2023 · 8 comments
Labels
area/analyze Issues or PRs related to `odo analyze` / Alizer kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo)

Comments

@feloy
Copy link
Contributor

feloy commented May 9, 2023

/kind feature

Parent user story: #6669

Which functionality do you think we should add?

As a user, I would like that Alizer returns a Devfile compatible with architectures I gave it.

Why is this needed?

NOTES:

@openshift-ci openshift-ci bot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label May 9, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label May 9, 2023
@rm3l
Copy link
Member

rm3l commented Jul 6, 2023

Grooming (Jul 6, 2023)

@thepetk to create an issue in Alizer

@rm3l rm3l added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels Jul 6, 2023
@thepetk
Copy link
Contributor

thepetk commented Jul 6, 2023

@thepetk to create an issue in Alizer

Issue created here: devfile/api#1181

@rm3l
Copy link
Member

rm3l commented Jul 6, 2023

Thanks @thepetk!

@rm3l rm3l added status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo) and removed triage/needs-information Indicates an issue needs more information in order to work on it. labels Jul 7, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 6, 2023

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 the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 6, 2023
Copy link
Contributor

github-actions bot commented Nov 5, 2023

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Nov 5, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Nov 5, 2023
@thepetk thepetk moved this from Done ✅ to To Do 📝 in odo Project Nov 6, 2023
@thepetk thepetk moved this from To Do 📝 to Done ✅ in odo Project Nov 6, 2023
@thepetk
Copy link
Contributor

thepetk commented Nov 6, 2023

@rm3l this is still open in alizer side (to add support for the architectures). We are waiting the creation of more filters in devfile API

@rm3l
Copy link
Member

rm3l commented Nov 6, 2023

@rm3l this is still open in alizer side (to add support for the architectures). We are waiting the creation of more filters in devfile API

Right - reopening then.

/reopen
/remove-lifecycle stale
/remove-lifecycle rotten
/lifecycle frozen

Copy link

openshift-ci bot commented Nov 6, 2023

@rm3l: Reopened this issue.

In response to this:

@rm3l this is still open in alizer side (to add support for the architectures). We are waiting the creation of more filters in devfile API

Right - reopening then.

/reopen
/remove-lifecycle stale
/remove-lifecycle rotten
/lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot reopened this Nov 6, 2023
@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 6, 2023
@github-project-automation github-project-automation bot moved this from Done ✅ to To Do 📝 in odo Project Nov 6, 2023
@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Nov 6, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Nov 6, 2023
@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Nov 6, 2023
@rm3l rm3l added the area/analyze Issues or PRs related to `odo analyze` / Alizer label Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/analyze Issues or PRs related to `odo analyze` / Alizer kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo)
Projects
Status: To Do 📝
Development

No branches or pull requests

3 participants