-
Notifications
You must be signed in to change notification settings - Fork 243
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
Comments
Grooming (Jul 6, 2023) @thepetk to create an issue in Alizer |
Issue created here: devfile/api#1181 |
Thanks @thepetk! |
A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
@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 |
@rm3l: Reopened this issue. In response to this:
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. |
/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:
The text was updated successfully, but these errors were encountered: