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

Default registry migration #2961

Closed
GeekArthur opened this issue Apr 22, 2020 · 2 comments
Closed

Default registry migration #2961

GeekArthur opened this issue Apr 22, 2020 · 2 comments
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@GeekArthur
Copy link
Contributor

/kind feature
/area devfile

Which functionality do you think we should add?

Currently the default registry is hosted on Elson's personal Github repository https://github.com/elsony/devfile-registry/tree/master/devfiles. The original idea regarding default registry was to let it host on personal git repository for tech preview as it's easier to manage and manipulate for both testing and development. We should let the default registry host on org Github repository or somewhere else.

Why is this needed?

Since we decide to support dynamic registry support, so list personal Github repository as default for user is not ideal and OK
@openshift-ci-robot openshift-ci-robot added kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. labels Apr 22, 2020
@GeekArthur GeekArthur mentioned this issue Apr 22, 2020
Merged
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 21, 2020
@GeekArthur
Copy link
Contributor Author

The default registry has been migrated to https://github.com/odo-devfiles/registry/, so close this one. We might need to migrate the registry to OCI-based registry in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@openshift-bot @GeekArthur @openshift-ci-robot