I've tried to follow the documentation (Pentaho Multi-Tenancy) but the way they did isn't exactly what I need, they still use only one repository. I'm trying to find a way to make the server use one repository for each tenant. Is that possible?
I've found some classes like: Tenant (Tenant (pentaho-platform-core 8.1.0.0-365 API)) and RepositoryTenantManager (RepositoryTenantManager (pentaho-platform-repository 8.1.0.0-365 API) ). The documentation about them is vague, are they used?
As far as I know, you can’t. Pentaho uses only one repo, at most you can limit what each user can see and onky show elements of the right tenant.
Related
I'm using swaggydoc plugin on my grails application to document the REST APIs. I have two versions of API, v0 and v1 and corresponding controllers with same name, one for each version like:
directory structure
and i have the Url mapping like "/my2api/v1"(controller:"api",namespace:'v1')
"/myapi/v0" (controller:"api", namespace:'v0')
and getting both versions of the API endpoints listed as /myapi/v0/activeContracts like here.
So my question is, how can I get the API end point listed with correct URLs with corresponding versions like /myapi/v0/activeContracts & /myapi/v1/activeContracts as i mentioned I've tried the mapping but it ill just pickup the first the last mapping and assign it to both versions.
Any help would be greatly appreciated.
For people facing the same prob, I couldn't find a solution using swaggyDocs and also came across some post suggesting it doesn't support API versioning so ended up switching to Grails RestApiDoc which provides a lot more control (changing the API conf by just editing the json) than I was able to get on swaggyDocs. But please do post if someone knows a way to work it out in swaggyDoc.
I don't see a way to access "Issues in Feature" stories. Can someone point me in the right direction? Any help is greatly appreciated!
I'm using the JIRA latest API (I think 7.1.1), and can make other calls to get info from Jira, just haven't found a way to get the "child" stories from this section.
By Issues In Feature I assume you want to search for Stories (or other issue types) linked to an issue of type Feature.
If you use an add-on like Script Runner, you get access to additional JQL functions that allow you to query for issues linked to each other. Look here for its documentation.
The JQL you end up with can also be used in REST API calls.
I am using GitLab 6.9.2 e46b644, I can not find any API to rename a group from API doc, but from gitlab UI, it really support rename group.
any idea if I need to batch rename groups?
Thanks in advance.
As you've said, it's not documented at: https://github.com/gitlabhq/gitlabhq/blob/4a5044e30269f8b3c6c075093cd4646a478231c7/doc/api/groups.md
Also, it's not implemented at: https://github.com/gitlabhq/gitlabhq/blob/4a5044e30269f8b3c6c075093cd4646a478231c7/lib/api/groups.rb which would be the obvious place.
And I could not find any feature request at http://feedback.gitlab.com
So I think it is safe to assume that it is not possible. I recommend that you open a feature request at http://feedback.gitlab.com
I am trying to write a query in Ruby to insert a user story in Rally using WSAPI. I read through https://rally1.rallydev.com/slm/doc/webservice/.I looked it up and found that wsapi has a create() method, but I am not aware of its signature. I know it uses PUT/Post method for creation, but I just need an example to understand how to write create queries. Does anyone know of any useful resource to know more about this? I have all my code ready, just need information about writing "create" queries using Rally's WSAPI.
Thanks
There is a full directory of Ruby REST examples in the Github Repository for RallyRestToolkitForRuby:
https://github.com/RallyTools/RallyRestToolkitForRuby/tree/master/examples
This create example may be of particular interest. It's for a Defect, but the same logic would apply to Stories:
04-create-defect.rb
I'd like to keep a log of all searches that users do on my site which uses the sunspot-rails gem. I don't need the logs to be real-time accessible by my application as they're for analytics that will be processed later.
I'm thinking that I should do the logging in rails rather than in solr itself so that I have access to the entire session, but I'm not sure how to build that. Is there a standard method for this? I saw this question but I would think there would be something more generic than writing it all myself in ApplicationController.
The ultimate answer depends on howwhere you're implementing your search. If you have a single search controller, do the logging there. If you have a collection of search controllers, either do it in each one, or create a base class, do the filter/logging in the base class.
Can you provide any more details?