-
Notifications
You must be signed in to change notification settings - Fork 474
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
Allow to install and list all the community add-ons #2137
Comments
I like the idea to install
and for the tagged addons
if, by default, the project is cloned from master or another branch, we need also a way to update it
|
-1 for using community keyword here. When we are talking about an upstream project, everything in the project means community. We can provide a way to list the catalogue and as @cmoulliard said a way to update the add-ons. But at this point it is not a priority. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Adding functionality to list community add-ons would be an overkill IMO, then we need to decide which github repos containing add-ons we would fetch the add-ons list from.. which should be configurable by the user. Remote install which is #635 can be implemented and would be nice feature. But right now the add-ons in the repo are directories, we need to package them in tar balls which can be downloaded, and then we extract it and do the regular add-on install. |
@budhram Big 👍 for the ability to list, install and update the addons from the community repository. It would also help the users to have more up-to-date addons. Last but not least this feature would lower the pressure to release CDK with all addons up-to-date, if there is a bad timing of CDK and eap-cd/xpaas/che releases it would not be big problem no longer. We could just update the repository and users can easily update the addons. WDYT? @LalatenduMohanty |
The another aspect is if we allow this then we might need to keep our community add-ons update to date and workable all the time else if user try to install/apply community add-on and found that it is not working it is likely that he would create issues. |
@cmoulliard asked me
and at present, we don't have such mechanism.
A similar issue we have #635 which is to install addon from the remote location.
My idea here is, for above usecase, we can
minishift addons list --community
( suggest for different flag )minishift addons install --community ansible-service-broker
This should download the specied add-on directory from the minishift-addon repo and place into the require location.
WDYT @minishift/minishift-dev ?
The text was updated successfully, but these errors were encountered: