-
-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is Jira supported for issue alerts? #278
Comments
Same issue here. Looks like it fails parsing the response when there are nested objects as its defined as a simple |
Im wondering if it makes more sense to handle the actions and other highly configurable properties similar to this resource: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_policy.html |
I have made #
# Create a Jira Ticket
#
data "sentry_organization_integration" "jira" {
organization = sentry_project.test.organization
provider_key = "jira"
name = "JIRA" # Name of your Jira server
}
resource "sentry_issue_alert" "jira_alert" {
actions = <<EOT
[
{
"id": "sentry.integrations.jira.notify_action.JiraCreateTicketAction",
"integration": ${parseint(data.sentry_organization_integration.jira.id, 10)},
"project": "349719"
"issueType": "1"
}
]
EOT
// ...
} |
I've created a manually configured action in Sentry. The action registers a JIRA issue with a set component, and it works really well.
Since we have lots of projects and I'd like to automate the rule across them all, I've attempted to copy the existing action over to a new terraform resource as mentioned as a tip in the configuration.
However I'm faced with this error:
So I'm wondering if JIRA is supported, and if anyone else has had more luck with similar scenarios?
The text was updated successfully, but these errors were encountered: