Skip to content

Conversation

@someone-stole-my-name
Copy link

Description

Remove the docker alert type. It may have existed in the past? There's no documentation on https://pan.dev/search/?q=alert-profiles about this endpoint.

Motivation and Context

Otherwise creating webhooks fail with: ... Non-OK status: 400 (invalid alert type docker)

How Has This Been Tested?

Manually on our tenant.

resource "prismacloudcompute_alertprofile" "foo" {
  name                                    = "foo"
  enable_immediate_vulnerabilities_alerts = true
  webhook {
    url         = "xxxx"
    custom_json = <<-EOT
{
    "text": "type: #type"
}
EOT
  }

  policy {
    container_vulnerability {
      enabled   = true
      all_rules = false
      rules = [prismacloudcompute_image_vulnerability_policy.foo.rule[0].name]
    }
  }
}

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes if appropriate.
  • All new and existing tests passed. existing ones are broken 😢

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant