You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
The text was updated successfully, but these errors were encountered:
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.
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...
The text was updated successfully, but these errors were encountered: