Code Monkey home page Code Monkey logo

Comments (5)

cf-gitbot avatar cf-gitbot commented on July 26, 2024

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/144884173

The labels on this github issue will be updated when the story is started.

from cli-plugin-repo.

n4wei avatar n4wei commented on July 26, 2024

Hi @diegovinas. The plugin information is stored locally in your home directory by default ($HOME/.cf/plugin/). Could it be that the other users are not sharing the same home directory as you? There is an environment variable CF_PLUGIN_HOME that allows you to set the home directory used for plugins. You can share your plugin home directory with others this way.

from cli-plugin-repo.

diegovinas avatar diegovinas commented on July 26, 2024

Hi @nickwei84, I was under the impression that when the custom CLIPR owner pushes it to CF and runs "cf add-plugin-repo", the repo is available to every CLI user accessing from their own computers. I guess every user needs to run "cf add-plugin-repo" to be able to "see/install' to the plugins in the custom CLIPR.

At least that worked for me.

However, typically CLI users may use their own computer to run cf commands (not a shared computer) so ideally "adding" the repo should not have to be done by every user. Just a suggestion.

from cli-plugin-repo.

n4wei avatar n4wei commented on July 26, 2024

@diegovinas You are correct that each user on a different machine/user profile will, by default, need to add the plugin repository. You have a good idea, however sharing plugin repos becomes a much more difficult feat when doing so amongst users with different levels of authorization, as well as managing permissions. Currently the cloud controller API does not support sharing plugin repos amongst multiple users. Please feel free to submit a feature request to the cloud controller API here: https://github.com/cloudfoundry/cloud_controller_ng.

from cli-plugin-repo.

diegovinas avatar diegovinas commented on July 26, 2024

Since there is a workaround (each user executing "cf add-plugin-repo" in order to see/install a plugin in that repo) and the feature needs to be implemented in the API first, I'm closing this item. Thanks you @nickwei84 for the clarification.

from cli-plugin-repo.

Related Issues (19)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.