JIRA Software RAML for Mulesoft Integration

[Pranjal Shukla]

We would like to onboard JIRA API's to Mulesoft using RAML specification. Is there a way where we can convert an existing JIRA WADl to RAML, has anybody tried that?

We are doing this for better API governance and would like to block certain REST API's for some users, especially the Admin ones (Operations that are performed by SysAdmins).

Any leads should help.

[Nic Brough -Adaptavist-]

No, you'll need to do all the work of conversion by hand, translating the bits you think you want.

Jira's REST API respects the permissions within the system, there's no need to block API access by user - all you have to do to stop them using admin functions over REST is not give them Admin rights in the application.  There are some REST APIs that, if blocked, will stop the application working in the UI as well.

You really don't want to be doing any REST API blocking.

[Pranjal Shukla]

Thanks Nic,

Note that we intend to block the API's only from Mulesoft Gateway and not permanently from every channel (UI and REST accessed from non mulesoft channel).

We just want to avoid any untoward situation because mulesoft platform is a shared platform in our organization and mulesoft developer have access to most of the resources. We want to avoid any inadvertent operation that may lead to deletion of some artifacts from the instance hence we want to block some API's.

Coming to API Spec, i see that Atlasssian has published WADL for JIRA REST API but when I try to convert that to RAML, it fails as it flags too many errors. I tried on appmatic.io

Is there a way we can generate a RAML specification of current REST API? 

[Nic Brough -Adaptavist-]

As I said, you'll need to convert it by hand if your tool can't do it.