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

Feature request: Allow for specifying Catalog location thru admin UI. #2672

Closed
srikarm opened this issue Nov 13, 2015 · 2 comments
Closed

Feature request: Allow for specifying Catalog location thru admin UI. #2672

srikarm opened this issue Nov 13, 2015 · 2 comments
Labels
area/catalog kind/enhancement Issues that improve or augment existing functionality

Comments

@srikarm
Copy link

srikarm commented Nov 13, 2015

Currently one need to update the API via a POST request to change the location of the rancher-catalog repo location. While it works fine, it would be good to have the feature enabled via UI screen. Also, it would be a great feature to set catalog per environment...for example, it our use case, we would like to create an environment for different product groups and have each product group have their own catalog. It could be a scenario like Catalog items marked as generally available to all + items limited to a product group/environment. By default all environments would inherit default catalog but admin could change that to specific repo...

@deniseschannon deniseschannon added kind/enhancement Issues that improve or augment existing functionality area/ui area/catalog labels Nov 13, 2015
@vincent99
Copy link
Contributor

This is several different requests..

  • Supporting more than one catalog repo will be in the next full release (it's actually merged, Support for multiple catalog repos. rancher-catalog-service#20)
  • Configuring the catalog URL(s) in the UI for admins will probably ship with that. (Side note: you can go to the API and change the setting with just a browser, you don't actually need API keys and curl or similar... User menu -> API & Keys -> click Endpoint link and then navigate to /v1/settings/catalog.url and click the blue Edit button)
  • Access controls for different catalog items for different people/environments is not in the immediate roadmap. The catalog service runs as a separate API that has no information about what user or environment the request is for.

@will-chan
Copy link
Contributor

Added new feature to track 3rd feature request in #3158. Closing this issue as the 1st two items have already been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/catalog kind/enhancement Issues that improve or augment existing functionality
Projects
None yet
Development

No branches or pull requests

4 participants