Hey, we have a use-case where we want to programmatically install forge/connect-on-forge applications. As far as I understand, the only way to do this is using GraphQL API, UPM works only for connect applications.
We have everything setup and running fine in developer instance. Application gets installed in the given jira instance. The same setup fails to work on production Jira instance.
The following query triggers installation, but results in an error
Install trigger mutation
mutation applicationInstallation($input: AppInstallationInput!) {
installApp(input: $input) {
success
taskId
errors {
message
extensions {
errorType
}
}
}
}
variables
{
"input": {
"installationContext": "ari:cloud:jira::site/....",
"appId": "ari:cloud:ecosystem::app/.....",
"environmentKey": "production"
}
}
Polling for the status of the given installation results in
{
"data": {
"appInstallationTask": {
"state": "FAILED",
"errors": [
{
"message": "An unexpected error occurred",
"extensions": {
"errorType": "INTERNAL_SERVER_ERROR",
"statusCode": 500
}
}
]
}
},
"extensions": {
"gateway": {
"request_id": "38b8a6b1-8d05-4406-8bad-f3a7fc28686e",
"trace_id": "bbbe01b698794073b3cbb9f22e6cad15",
"crossRegion": false,
"edgeCrossRegion": false
}
}
}
Installation taskId is “ff65f349-90a8-4312-b936-f734e4078572”
Is there any way to find more about what causes the issue. What is the difference between dev and production instances in this case?
Edit: I tried the same setup, but attempting to install “free” application, and it works on both dev and production jira. Could it be related to some licensing limitations of Forge&GraphQL API, or user permissions. For authorization of such requests we use API token?