create new tag
, view all tags

JiraRestPluginDev Discussion: Page for developer collaboration, enhancement requests, patches and improved versions on JiraRestPlugin contributed by the TWikiCommunity.
• Please let us know what you think of this extension.
• For support, check the existing questions, or ask a new support question in the Support web!
• Please file bug reports in the JiraRestPlugin bug database.

Feedback on JiraRestPlugin

Initial version is now uploaded. Enjoy!

Idea for enhancement:

  • Possible to select a subset of the returned JSON using a JSON Path, such as: $(content.key)
  • Possible to issue a chain of API calls
  • Possible to select JSON array reference, reference more than one level deep, such as: $(content.issues[*].key)
  • Add format and separator parameters to format the output, such as: format="| [[$url][$key]] | $summary | $description |"
  • Support multiple REST domains in configure, with a server="" parameter to select the REST domain ID

-- Peter Thoeny - 2015-06-08

The related JiraPlugin is designed to display JIRA issues as a TWiki table, using JQL (JIRA Query Language).

-- Peter Thoeny - 2015-06-08

I just noticed that this plugin is generic enough, it can used to establish REST connections to data sources other than JIRA. Possibly rename this plugin to RestCallPlugin, and rename %JIRAREST{}% to %RESTCALL{}%?

-- Peter Thoeny - 2015-06-10

Thinking about using this as a front end for ISAM webservices (http://www-03.ibm.com/software/products/en/access-mgr-web). Things I've tweaked on my side to make it work:

  1. Removed RestBase as a requirement - I need to be able to hit things as simple as https://<hostname>/<somethingSimple>
  2. Added $ENV{PERL_LWP_SSL_VERIFY_HOSTNAME}=0; so that I could access https with little effort

Actually, that's about it!

-- Aaron Walker - 2015-09-10


1. Wouldn't {RestDomain} = "https://<hostname>", {RestBase} = "/" and command="<somethingSimple>" work?

2. Where did you add $ENV{PERL_LWP_SSL_VERIFY_HOSTNAME}=0; ? FYI, you should by able to add it to twiki/lib/LocalSite.cfg

-- Peter Thoeny - 2015-09-16

for (1), when I do that, I get (in the debug log): | 2015-09-17 - 09:46 | - JiraRestPlugin::Core: ERROR: POST '/pdadmin' returns code 404 I don't know if that's because it is prefixing a '/' here: $command = "/$command" unless( $command =~ /^\// );

for (2), I added it in directly before the REST::Client->new(). As for adding it to LocalSite.cfg, I don't know about the desirability of that - would that possibly have unintended consequences for other plugins?

I guess another wish list item would be the ability to specify multiple RestDomains, perhaps in the same manner that you suggested for the TrackerPlugin


-- Aaron Walker - 2015-09-17

1. I think it is safe to remove that prefix, since it is documented to start with a slash. Can you comment that out an confirm if it works properly for your case?

2. Potentially yes because other certs would not be checked as well. I think I leave the plugins docs as is with the LocalSite.cfg recommendation (I tested that to work properly).

3. I added a new "Support multiple REST domains in configure" enhancement idea at the top.

-- Peter Thoeny - 2015-09-18

Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r6 - 2015-09-18 - PeterThoeny
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.