Docs Home Pulumi IaC Pulumi ESC Pulumi Insights Pulumi Cloud Packages Tutorials
  1. Packages
  2. Incapsula Provider
  3. API Docs
  4. NotificationCenterPolicy
incapsula 3.33.0 published on Wednesday, Apr 30, 2025 by imperva
imperva/terraform-provider-incapsula

incapsula.NotificationCenterPolicy

Explore with Pulumi AI

incapsula logo
incapsula 3.33.0 published on Wednesday, Apr 30, 2025 by imperva
imperva/terraform-provider-incapsula

    Provides an Incapsula Notification Center Policy resource.

    Example Usage

    Notification center policy that applies on subaccounts

    import * as pulumi from "@pulumi/pulumi";
import * as incapsula from "@pulumi/incapsula";

const notification_policy_subaccount = new incapsula.NotificationCenterPolicy("notification-policy-subaccount", {
    accountId: 12345,
    policyName: "Terraform policy sub account",
    status: "ENABLE",
    subCategory: "SITE_NOTIFICATIONS",
    emailchannelUserRecipientLists: [
        1111,
        2222,
    ],
    emailchannelExternalRecipientLists: [
        "john.doe@company.com",
        "another.email@company.com",
    ],
    policyType: "SUB_ACCOUNT",
    subAccountLists: [
        123456,
        incapsula_subaccount["tmp-subaccount"].id,
    ],
});

    import pulumi
import pulumi_incapsula as incapsula

notification_policy_subaccount = incapsula.NotificationCenterPolicy("notification-policy-subaccount",
    account_id=12345,
    policy_name="Terraform policy sub account",
    status="ENABLE",
    sub_category="SITE_NOTIFICATIONS",
    emailchannel_user_recipient_lists=[
        1111,
        2222,
    ],
    emailchannel_external_recipient_lists=[
        "john.doe@company.com",
        "another.email@company.com",
    ],
    policy_type="SUB_ACCOUNT",
    sub_account_lists=[
        123456,
        incapsula_subaccount["tmp-subaccount"]["id"],
    ])

    package main

import (
	"github.com/pulumi/pulumi-terraform-provider/sdks/go/incapsula/v3/incapsula"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := incapsula.NewNotificationCenterPolicy(ctx, "notification-policy-subaccount", &incapsula.NotificationCenterPolicyArgs{
			AccountId:   pulumi.Float64(12345),
			PolicyName:  pulumi.String("Terraform policy sub account"),
			Status:      pulumi.String("ENABLE"),
			SubCategory: pulumi.String("SITE_NOTIFICATIONS"),
			EmailchannelUserRecipientLists: pulumi.Float64Array{
				pulumi.Float64(1111),
				pulumi.Float64(2222),
			},
			EmailchannelExternalRecipientLists: pulumi.StringArray{
				pulumi.String("john.doe@company.com"),
				pulumi.String("another.email@company.com"),
			},
			PolicyType: pulumi.String("SUB_ACCOUNT"),
			SubAccountLists: pulumi.Float64Array{
				pulumi.Float64(123456),
				incapsula_subaccount.TmpSubaccount.Id,
			},
		})
		if err != nil {
			return err
		}
		return nil
	})
}

    using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Incapsula = Pulumi.Incapsula;

return await Deployment.RunAsync(() => 
{
    var notification_policy_subaccount = new Incapsula.NotificationCenterPolicy("notification-policy-subaccount", new()
    {
        AccountId = 12345,
        PolicyName = "Terraform policy sub account",
        Status = "ENABLE",
        SubCategory = "SITE_NOTIFICATIONS",
        EmailchannelUserRecipientLists = new[]
        {
            1111,
            2222,
        },
        EmailchannelExternalRecipientLists = new[]
        {
            "john.doe@company.com",
            "another.email@company.com",
        },
        PolicyType = "SUB_ACCOUNT",
        SubAccountLists = new[]
        {
            123456,
            incapsula_subaccount.Tmp_subaccount.Id,
        },
    });

});

    package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.incapsula.NotificationCenterPolicy;
import com.pulumi.incapsula.NotificationCenterPolicyArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var notification_policy_subaccount = new NotificationCenterPolicy("notification-policy-subaccount", NotificationCenterPolicyArgs.builder()
            .accountId(12345)
            .policyName("Terraform policy sub account")
            .status("ENABLE")
            .subCategory("SITE_NOTIFICATIONS")
            .emailchannelUserRecipientLists(            
                1111,
                2222)
            .emailchannelExternalRecipientLists(            
                "john.doe@company.com",
                "another.email@company.com")
            .policyType("SUB_ACCOUNT")
            .subAccountLists(            
                123456,
                incapsula_subaccount.tmp-subaccount().id())
            .build());

    }
}

    resources:
  notification-policy-subaccount:
    type: incapsula:NotificationCenterPolicy
    properties:
      accountId: 12345
      policyName: Terraform policy sub account
      status: ENABLE
      subCategory: SITE_NOTIFICATIONS
      emailchannelUserRecipientLists:
        - 1111
        - 2222
      emailchannelExternalRecipientLists:
        - john.doe@company.com
        - another.email@company.com
      policyType: SUB_ACCOUNT
      subAccountLists:
        - 123456
        - ${incapsula_subaccount"tmp-subaccount"[%!s(MISSING)].id}

    Notification policy that applies to assets of type “incapsula.Site”

    import * as pulumi from "@pulumi/pulumi";
import * as incapsula from "@pulumi/incapsula";

const notification_policy_account_with_assets = new incapsula.NotificationCenterPolicy("notification-policy-account-with-assets", {
    accountId: 12345,
    policyName: "Terraform policy account with assets",
    assets: [
        {
            assetType: "SITE",
            assetId: incapsula_site["tmp-site"].id,
        },
        {
            assetType: "SITE",
            assetId: 7999203,
        },
    ],
    status: "ENABLE",
    subCategory: "SITE_NOTIFICATIONS",
    emailchannelUserRecipientLists: [
        1111,
        2222,
    ],
    emailchannelExternalRecipientLists: [
        "john.doe@company.com",
        "another.exernal.email@company.com",
    ],
    policyType: "ACCOUNT",
    applyToNewAssets: "FALSE",
});

    import pulumi
import pulumi_incapsula as incapsula

notification_policy_account_with_assets = incapsula.NotificationCenterPolicy("notification-policy-account-with-assets",
    account_id=12345,
    policy_name="Terraform policy account with assets",
    assets=[
        {
            "asset_type": "SITE",
            "asset_id": incapsula_site["tmp-site"]["id"],
        },
        {
            "asset_type": "SITE",
            "asset_id": 7999203,
        },
    ],
    status="ENABLE",
    sub_category="SITE_NOTIFICATIONS",
    emailchannel_user_recipient_lists=[
        1111,
        2222,
    ],
    emailchannel_external_recipient_lists=[
        "john.doe@company.com",
        "another.exernal.email@company.com",
    ],
    policy_type="ACCOUNT",
    apply_to_new_assets="FALSE")

    package main

import (
	"github.com/pulumi/pulumi-terraform-provider/sdks/go/incapsula/v3/incapsula"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := incapsula.NewNotificationCenterPolicy(ctx, "notification-policy-account-with-assets", &incapsula.NotificationCenterPolicyArgs{
			AccountId:  pulumi.Float64(12345),
			PolicyName: pulumi.String("Terraform policy account with assets"),
			Assets: incapsula.NotificationCenterPolicyAssetArray{
				&incapsula.NotificationCenterPolicyAssetArgs{
					AssetType: pulumi.String("SITE"),
					AssetId:   pulumi.Any(incapsula_site.TmpSite.Id),
				},
				&incapsula.NotificationCenterPolicyAssetArgs{
					AssetType: pulumi.String("SITE"),
					AssetId:   pulumi.Float64(7999203),
				},
			},
			Status:      pulumi.String("ENABLE"),
			SubCategory: pulumi.String("SITE_NOTIFICATIONS"),
			EmailchannelUserRecipientLists: pulumi.Float64Array{
				pulumi.Float64(1111),
				pulumi.Float64(2222),
			},
			EmailchannelExternalRecipientLists: pulumi.StringArray{
				pulumi.String("john.doe@company.com"),
				pulumi.String("another.exernal.email@company.com"),
			},
			PolicyType:       pulumi.String("ACCOUNT"),
			ApplyToNewAssets: pulumi.String("FALSE"),
		})
		if err != nil {
			return err
		}
		return nil
	})
}

    using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Incapsula = Pulumi.Incapsula;

return await Deployment.RunAsync(() => 
{
    var notification_policy_account_with_assets = new Incapsula.NotificationCenterPolicy("notification-policy-account-with-assets", new()
    {
        AccountId = 12345,
        PolicyName = "Terraform policy account with assets",
        Assets = new[]
        {
            new Incapsula.Inputs.NotificationCenterPolicyAssetArgs
            {
                AssetType = "SITE",
                AssetId = incapsula_site.Tmp_site.Id,
            },
            new Incapsula.Inputs.NotificationCenterPolicyAssetArgs
            {
                AssetType = "SITE",
                AssetId = 7999203,
            },
        },
        Status = "ENABLE",
        SubCategory = "SITE_NOTIFICATIONS",
        EmailchannelUserRecipientLists = new[]
        {
            1111,
            2222,
        },
        EmailchannelExternalRecipientLists = new[]
        {
            "john.doe@company.com",
            "another.exernal.email@company.com",
        },
        PolicyType = "ACCOUNT",
        ApplyToNewAssets = "FALSE",
    });

});

    package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.incapsula.NotificationCenterPolicy;
import com.pulumi.incapsula.NotificationCenterPolicyArgs;
import com.pulumi.incapsula.inputs.NotificationCenterPolicyAssetArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var notification_policy_account_with_assets = new NotificationCenterPolicy("notification-policy-account-with-assets", NotificationCenterPolicyArgs.builder()
            .accountId(12345)
            .policyName("Terraform policy account with assets")
            .assets(            
                NotificationCenterPolicyAssetArgs.builder()
                    .assetType("SITE")
                    .assetId(incapsula_site.tmp-site().id())
                    .build(),
                NotificationCenterPolicyAssetArgs.builder()
                    .assetType("SITE")
                    .assetId(7999203)
                    .build())
            .status("ENABLE")
            .subCategory("SITE_NOTIFICATIONS")
            .emailchannelUserRecipientLists(            
                1111,
                2222)
            .emailchannelExternalRecipientLists(            
                "john.doe@company.com",
                "another.exernal.email@company.com")
            .policyType("ACCOUNT")
            .applyToNewAssets("FALSE")
            .build());

    }
}

    resources:
  notification-policy-account-with-assets:
    type: incapsula:NotificationCenterPolicy
    properties:
      accountId: 12345
      policyName: Terraform policy account with assets
      assets:
        - assetType: SITE
          assetId: ${incapsula_site"tmp-site"[%!s(MISSING)].id}
        - assetType: SITE
          assetId: 7.999203e+06
      status: ENABLE
      subCategory: SITE_NOTIFICATIONS
      emailchannelUserRecipientLists:
        - 1111
        - 2222
      emailchannelExternalRecipientLists:
        - john.doe@company.com
        - another.exernal.email@company.com
      policyType: ACCOUNT
      applyToNewAssets: FALSE

    Notification policy on sub-category with no relevance to assets

    import * as pulumi from "@pulumi/pulumi";
import * as incapsula from "@pulumi/incapsula";

const notification_policy_account_without_assets = new incapsula.NotificationCenterPolicy("notification-policy-account-without-assets", {
    accountId: 12345,
    emailchannelExternalRecipientLists: [
        "john.doe@company.com",
        "another.exernal.email@company.com",
    ],
    emailchannelUserRecipientLists: [
        1111,
        2222,
    ],
    policyName: "Terraform policy account without assets",
    policyType: "ACCOUNT",
    status: "ENABLE",
    subCategory: "ACCOUNT_NOTIFICATIONS",
});

    import pulumi
import pulumi_incapsula as incapsula

notification_policy_account_without_assets = incapsula.NotificationCenterPolicy("notification-policy-account-without-assets",
    account_id=12345,
    emailchannel_external_recipient_lists=[
        "john.doe@company.com",
        "another.exernal.email@company.com",
    ],
    emailchannel_user_recipient_lists=[
        1111,
        2222,
    ],
    policy_name="Terraform policy account without assets",
    policy_type="ACCOUNT",
    status="ENABLE",
    sub_category="ACCOUNT_NOTIFICATIONS")

    package main

import (
	"github.com/pulumi/pulumi-terraform-provider/sdks/go/incapsula/v3/incapsula"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := incapsula.NewNotificationCenterPolicy(ctx, "notification-policy-account-without-assets", &incapsula.NotificationCenterPolicyArgs{
			AccountId: pulumi.Float64(12345),
			EmailchannelExternalRecipientLists: pulumi.StringArray{
				pulumi.String("john.doe@company.com"),
				pulumi.String("another.exernal.email@company.com"),
			},
			EmailchannelUserRecipientLists: pulumi.Float64Array{
				pulumi.Float64(1111),
				pulumi.Float64(2222),
			},
			PolicyName:  pulumi.String("Terraform policy account without assets"),
			PolicyType:  pulumi.String("ACCOUNT"),
			Status:      pulumi.String("ENABLE"),
			SubCategory: pulumi.String("ACCOUNT_NOTIFICATIONS"),
		})
		if err != nil {
			return err
		}
		return nil
	})
}

    using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Incapsula = Pulumi.Incapsula;

return await Deployment.RunAsync(() => 
{
    var notification_policy_account_without_assets = new Incapsula.NotificationCenterPolicy("notification-policy-account-without-assets", new()
    {
        AccountId = 12345,
        EmailchannelExternalRecipientLists = new[]
        {
            "john.doe@company.com",
            "another.exernal.email@company.com",
        },
        EmailchannelUserRecipientLists = new[]
        {
            1111,
            2222,
        },
        PolicyName = "Terraform policy account without assets",
        PolicyType = "ACCOUNT",
        Status = "ENABLE",
        SubCategory = "ACCOUNT_NOTIFICATIONS",
    });

});

    package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.incapsula.NotificationCenterPolicy;
import com.pulumi.incapsula.NotificationCenterPolicyArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var notification_policy_account_without_assets = new NotificationCenterPolicy("notification-policy-account-without-assets", NotificationCenterPolicyArgs.builder()
            .accountId(12345)
            .emailchannelExternalRecipientLists(            
                "john.doe@company.com",
                "another.exernal.email@company.com")
            .emailchannelUserRecipientLists(            
                1111,
                2222)
            .policyName("Terraform policy account without assets")
            .policyType("ACCOUNT")
            .status("ENABLE")
            .subCategory("ACCOUNT_NOTIFICATIONS")
            .build());

    }
}

    resources:
  notification-policy-account-without-assets:
    type: incapsula:NotificationCenterPolicy
    properties:
      accountId: 12345
      emailchannelExternalRecipientLists:
        - john.doe@company.com
        - another.exernal.email@company.com
      emailchannelUserRecipientLists:
        - 1111
        - 2222
      policyName: Terraform policy account without assets
      policyType: ACCOUNT
      status: ENABLE
      subCategory: ACCOUNT_NOTIFICATIONS

    Create NotificationCenterPolicy Resource

    Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.

    Constructor syntax

    new NotificationCenterPolicy(name: string, args: NotificationCenterPolicyArgs, opts?: CustomResourceOptions);
    @overload
def NotificationCenterPolicy(resource_name: str,
                             args: NotificationCenterPolicyArgs,
                             opts: Optional[ResourceOptions] = None)

@overload
def NotificationCenterPolicy(resource_name: str,
                             opts: Optional[ResourceOptions] = None,
                             account_id: Optional[float] = None,
                             policy_name: Optional[str] = None,
                             sub_category: Optional[str] = None,
                             apply_to_new_assets: Optional[str] = None,
                             apply_to_new_sub_accounts: Optional[str] = None,
                             assets: Optional[Sequence[NotificationCenterPolicyAssetArgs]] = None,
                             emailchannel_external_recipient_lists: Optional[Sequence[str]] = None,
                             emailchannel_user_recipient_lists: Optional[Sequence[float]] = None,
                             notification_center_policy_id: Optional[str] = None,
                             policy_type: Optional[str] = None,
                             status: Optional[str] = None,
                             sub_account_lists: Optional[Sequence[float]] = None)
    func NewNotificationCenterPolicy(ctx *Context, name string, args NotificationCenterPolicyArgs, opts ...ResourceOption) (*NotificationCenterPolicy, error)
    public NotificationCenterPolicy(string name, NotificationCenterPolicyArgs args, CustomResourceOptions? opts = null)
    public NotificationCenterPolicy(String name, NotificationCenterPolicyArgs args)
public NotificationCenterPolicy(String name, NotificationCenterPolicyArgs args, CustomResourceOptions options)

    type: incapsula:NotificationCenterPolicy
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.

    Parameters

    name string
    The unique name of the resource.
    args NotificationCenterPolicyArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    resource_name str
    The unique name of the resource.
    args NotificationCenterPolicyArgs
    The arguments to resource properties.
    opts ResourceOptions
    Bag of options to control resource's behavior.
    ctx Context
    Context object for the current deployment.
    name string
    The unique name of the resource.
    args NotificationCenterPolicyArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args NotificationCenterPolicyArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args NotificationCenterPolicyArgs
    The arguments to resource properties.
    options CustomResourceOptions
    Bag of options to control resource's behavior.

    Constructor example

    The following reference example uses placeholder values for all input properties.

    var notificationCenterPolicyResource = new Incapsula.NotificationCenterPolicy("notificationCenterPolicyResource", new()
{
    AccountId = 0,
    PolicyName = "string",
    SubCategory = "string",
    ApplyToNewAssets = "string",
    ApplyToNewSubAccounts = "string",
    Assets = new[]
    {
        new Incapsula.Inputs.NotificationCenterPolicyAssetArgs
        {
            AssetType = "string",
            AssetId = 0,
        },
    },
    EmailchannelExternalRecipientLists = new[]
    {
        "string",
    },
    EmailchannelUserRecipientLists = new[]
    {
        0,
    },
    NotificationCenterPolicyId = "string",
    PolicyType = "string",
    Status = "string",
    SubAccountLists = new[]
    {
        0,
    },
});

    example, err := incapsula.NewNotificationCenterPolicy(ctx, "notificationCenterPolicyResource", &incapsula.NotificationCenterPolicyArgs{
	AccountId:             pulumi.Float64(0),
	PolicyName:            pulumi.String("string"),
	SubCategory:           pulumi.String("string"),
	ApplyToNewAssets:      pulumi.String("string"),
	ApplyToNewSubAccounts: pulumi.String("string"),
	Assets: incapsula.NotificationCenterPolicyAssetArray{
		&incapsula.NotificationCenterPolicyAssetArgs{
			AssetType: pulumi.String("string"),
			AssetId:   pulumi.Float64(0),
		},
	},
	EmailchannelExternalRecipientLists: pulumi.StringArray{
		pulumi.String("string"),
	},
	EmailchannelUserRecipientLists: pulumi.Float64Array{
		pulumi.Float64(0),
	},
	NotificationCenterPolicyId: pulumi.String("string"),
	PolicyType:                 pulumi.String("string"),
	Status:                     pulumi.String("string"),
	SubAccountLists: pulumi.Float64Array{
		pulumi.Float64(0),
	},
})

    var notificationCenterPolicyResource = new NotificationCenterPolicy("notificationCenterPolicyResource", NotificationCenterPolicyArgs.builder()
    .accountId(0)
    .policyName("string")
    .subCategory("string")
    .applyToNewAssets("string")
    .applyToNewSubAccounts("string")
    .assets(NotificationCenterPolicyAssetArgs.builder()
        .assetType("string")
        .assetId(0)
        .build())
    .emailchannelExternalRecipientLists("string")
    .emailchannelUserRecipientLists(0)
    .notificationCenterPolicyId("string")
    .policyType("string")
    .status("string")
    .subAccountLists(0)
    .build());

    notification_center_policy_resource = incapsula.NotificationCenterPolicy("notificationCenterPolicyResource",
    account_id=0,
    policy_name="string",
    sub_category="string",
    apply_to_new_assets="string",
    apply_to_new_sub_accounts="string",
    assets=[{
        "asset_type": "string",
        "asset_id": 0,
    }],
    emailchannel_external_recipient_lists=["string"],
    emailchannel_user_recipient_lists=[0],
    notification_center_policy_id="string",
    policy_type="string",
    status="string",
    sub_account_lists=[0])

    const notificationCenterPolicyResource = new incapsula.NotificationCenterPolicy("notificationCenterPolicyResource", {
    accountId: 0,
    policyName: "string",
    subCategory: "string",
    applyToNewAssets: "string",
    applyToNewSubAccounts: "string",
    assets: [{
        assetType: "string",
        assetId: 0,
    }],
    emailchannelExternalRecipientLists: ["string"],
    emailchannelUserRecipientLists: [0],
    notificationCenterPolicyId: "string",
    policyType: "string",
    status: "string",
    subAccountLists: [0],
});

    type: incapsula:NotificationCenterPolicy
properties:
    accountId: 0
    applyToNewAssets: string
    applyToNewSubAccounts: string
    assets:
        - assetId: 0
          assetType: string
    emailchannelExternalRecipientLists:
        - string
    emailchannelUserRecipientLists:
        - 0
    notificationCenterPolicyId: string
    policyName: string
    policyType: string
    status: string
    subAccountLists:
        - 0
    subCategory: string

    NotificationCenterPolicy Resource Properties

    To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.

    Inputs

    In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.

    The NotificationCenterPolicy resource accepts the following input properties:

    AccountId double
    Numeric identifier of the account to work on.
    PolicyName string
    The name of the policy. Cannot contain special characters
    SubCategory string
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    ApplyToNewAssets string
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    ApplyToNewSubAccounts string

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    Assets List<NotificationCenterPolicyAsset>
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    EmailchannelExternalRecipientLists List<string>
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    EmailchannelUserRecipientLists List<double>
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    NotificationCenterPolicyId string
    Unique identifier for the Notification Policy.
    PolicyType string
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    Status string
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    SubAccountLists List<double>
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    AccountId float64
    Numeric identifier of the account to work on.
    PolicyName string
    The name of the policy. Cannot contain special characters
    SubCategory string
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    ApplyToNewAssets string
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    ApplyToNewSubAccounts string

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    Assets []NotificationCenterPolicyAssetArgs
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    EmailchannelExternalRecipientLists []string
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    EmailchannelUserRecipientLists []float64
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    NotificationCenterPolicyId string
    Unique identifier for the Notification Policy.
    PolicyType string
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    Status string
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    SubAccountLists []float64
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    accountId Double
    Numeric identifier of the account to work on.
    policyName String
    The name of the policy. Cannot contain special characters
    subCategory String
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    applyToNewAssets String
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    applyToNewSubAccounts String

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    assets List<NotificationCenterPolicyAsset>
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    emailchannelExternalRecipientLists List<String>
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    emailchannelUserRecipientLists List<Double>
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    notificationCenterPolicyId String
    Unique identifier for the Notification Policy.
    policyType String
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    status String
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    subAccountLists List<Double>
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    accountId number
    Numeric identifier of the account to work on.
    policyName string
    The name of the policy. Cannot contain special characters
    subCategory string
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    applyToNewAssets string
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    applyToNewSubAccounts string

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    assets NotificationCenterPolicyAsset[]
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    emailchannelExternalRecipientLists string[]
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    emailchannelUserRecipientLists number[]
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    notificationCenterPolicyId string
    Unique identifier for the Notification Policy.
    policyType string
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    status string
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    subAccountLists number[]
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    account_id float
    Numeric identifier of the account to work on.
    policy_name str
    The name of the policy. Cannot contain special characters
    sub_category str
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    apply_to_new_assets str
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    apply_to_new_sub_accounts str

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    assets Sequence[NotificationCenterPolicyAssetArgs]
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    emailchannel_external_recipient_lists Sequence[str]
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    emailchannel_user_recipient_lists Sequence[float]
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    notification_center_policy_id str
    Unique identifier for the Notification Policy.
    policy_type str
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    status str
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    sub_account_lists Sequence[float]
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    accountId Number
    Numeric identifier of the account to work on.
    policyName String
    The name of the policy. Cannot contain special characters
    subCategory String
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    applyToNewAssets String
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    applyToNewSubAccounts String

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    assets List<Property Map>
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    emailchannelExternalRecipientLists List<String>
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    emailchannelUserRecipientLists List<Number>
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    notificationCenterPolicyId String
    Unique identifier for the Notification Policy.
    policyType String
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    status String
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    subAccountLists List<Number>
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.

    Outputs

    All input properties are implicitly available as output properties. Additionally, the NotificationCenterPolicy resource produces the following output properties:

    Id string
    The provider-assigned unique ID for this managed resource.
    Id string
    The provider-assigned unique ID for this managed resource.
    id String
    The provider-assigned unique ID for this managed resource.
    id string
    The provider-assigned unique ID for this managed resource.
    id str
    The provider-assigned unique ID for this managed resource.
    id String
    The provider-assigned unique ID for this managed resource.

    Look up Existing NotificationCenterPolicy Resource

    Get an existing NotificationCenterPolicy resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.

    public static get(name: string, id: Input<ID>, state?: NotificationCenterPolicyState, opts?: CustomResourceOptions): NotificationCenterPolicy
    @staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        account_id: Optional[float] = None,
        apply_to_new_assets: Optional[str] = None,
        apply_to_new_sub_accounts: Optional[str] = None,
        assets: Optional[Sequence[NotificationCenterPolicyAssetArgs]] = None,
        emailchannel_external_recipient_lists: Optional[Sequence[str]] = None,
        emailchannel_user_recipient_lists: Optional[Sequence[float]] = None,
        notification_center_policy_id: Optional[str] = None,
        policy_name: Optional[str] = None,
        policy_type: Optional[str] = None,
        status: Optional[str] = None,
        sub_account_lists: Optional[Sequence[float]] = None,
        sub_category: Optional[str] = None) -> NotificationCenterPolicy
    func GetNotificationCenterPolicy(ctx *Context, name string, id IDInput, state *NotificationCenterPolicyState, opts ...ResourceOption) (*NotificationCenterPolicy, error)
    public static NotificationCenterPolicy Get(string name, Input<string> id, NotificationCenterPolicyState? state, CustomResourceOptions? opts = null)
    public static NotificationCenterPolicy get(String name, Output<String> id, NotificationCenterPolicyState state, CustomResourceOptions options)
    resources:  _:    type: incapsula:NotificationCenterPolicy    get:      id: ${id}
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    resource_name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    The following state arguments are supported:
    AccountId double
    Numeric identifier of the account to work on.
    ApplyToNewAssets string
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    ApplyToNewSubAccounts string

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    Assets List<NotificationCenterPolicyAsset>
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    EmailchannelExternalRecipientLists List<string>
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    EmailchannelUserRecipientLists List<double>
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    NotificationCenterPolicyId string
    Unique identifier for the Notification Policy.
    PolicyName string
    The name of the policy. Cannot contain special characters
    PolicyType string
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    Status string
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    SubAccountLists List<double>
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    SubCategory string
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    AccountId float64
    Numeric identifier of the account to work on.
    ApplyToNewAssets string
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    ApplyToNewSubAccounts string

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    Assets []NotificationCenterPolicyAssetArgs
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    EmailchannelExternalRecipientLists []string
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    EmailchannelUserRecipientLists []float64
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    NotificationCenterPolicyId string
    Unique identifier for the Notification Policy.
    PolicyName string
    The name of the policy. Cannot contain special characters
    PolicyType string
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    Status string
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    SubAccountLists []float64
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    SubCategory string
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    accountId Double
    Numeric identifier of the account to work on.
    applyToNewAssets String
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    applyToNewSubAccounts String

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    assets List<NotificationCenterPolicyAsset>
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    emailchannelExternalRecipientLists List<String>
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    emailchannelUserRecipientLists List<Double>
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    notificationCenterPolicyId String
    Unique identifier for the Notification Policy.
    policyName String
    The name of the policy. Cannot contain special characters
    policyType String
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    status String
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    subAccountLists List<Double>
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    subCategory String
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    accountId number
    Numeric identifier of the account to work on.
    applyToNewAssets string
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    applyToNewSubAccounts string

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    assets NotificationCenterPolicyAsset[]
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    emailchannelExternalRecipientLists string[]
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    emailchannelUserRecipientLists number[]
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    notificationCenterPolicyId string
    Unique identifier for the Notification Policy.
    policyName string
    The name of the policy. Cannot contain special characters
    policyType string
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    status string
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    subAccountLists number[]
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    subCategory string
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    account_id float
    Numeric identifier of the account to work on.
    apply_to_new_assets str
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    apply_to_new_sub_accounts str

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    assets Sequence[NotificationCenterPolicyAssetArgs]
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    emailchannel_external_recipient_lists Sequence[str]
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    emailchannel_user_recipient_lists Sequence[float]
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    notification_center_policy_id str
    Unique identifier for the Notification Policy.
    policy_name str
    The name of the policy. Cannot contain special characters
    policy_type str
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    status str
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    sub_account_lists Sequence[float]
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    sub_category str
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.
    accountId Number
    Numeric identifier of the account to work on.
    applyToNewAssets String
    If value is TRUE, all newly onboarded assets are automatically added to the notification policy's assets list. Possible values: TRUE, FALSE (default value).
    We recommend always setting this field's value to FALSE, to disable automatic updates of assets on the policy, so you have full control over your resources.
    applyToNewSubAccounts String

    If value is TRUE, all newly onboarded sub accounts are automatically added to the notification policy's sub account list. Possible values: TRUE, FALSE (default value)
    Relevant if the policy_type is SUB_ACCOUNT.
    We recommend always setting this field's value to FALSE, to disable automatic updates of sub-accounts on the policy, so you have full control over your resources.

    <<<<<<< HEAD:website/docs/r/notification_policy.html.markdown Under the following conditions, you need to define at least 1 asset:
    If the policy_type argument is ACCOUNT, and the selected sub_category requires that the policy be applied to assets in the account, and the

    Under the following conditions, you need to define at least 1 asset: If the policy_type argument is ACCOUNT, and the chosen sub_category requires configuration of assets, and the

    docs-update:website/docs/r/notification_center_policy.html.markdown argument apply_to_new_assets is FALSE, then at least 1 asset must be defined.
    For example, when configuring a policy for the SITE_NOTIFICATIONS sub_category, if the argument apply_to_new_assets is FALSE, at least one SITE asset must be specified. The arguments that are supported in asset sub resource are:

    assets List<Property Map>
    Assets to receive notifications (if assets are relevant to the sub category type). Object struct: assetType: the asset type. Example: websites, router connections, network prefixes, individual IPs, Flow exporters assetId: the asset id.
    emailchannelExternalRecipientLists List<String>
    List of email addresses (for recipients who are not Imperva users) to receive email notifications. There must be at least one value in this list or in the emailchannel_user_recipient_list list.
    emailchannelUserRecipientLists List<Number>
    List of numeric identifiers of the users from the Imperva account to receive emails notifications. There must be at least one value in this list or in the emailchannel_external_recipient_list list.
    notificationCenterPolicyId String
    Unique identifier for the Notification Policy.
    policyName String
    The name of the policy. Cannot contain special characters
    policyType String
    If the value is ACCOUNT, the policy will apply only to the current account that is specified by the account_id. If the value is SUB_ACCOUNT the policy applies to the sub accounts only. The parent account will receive notifications for activity in the sub accounts that are specified in the sub_account_list parameter. This sub_account_list is available only in accounts that can contain sub accounts. Possible values: ACCOUNT (default value), SUB_ACCOUNT.
    status String
    Indicates whether the policy is enabled or disabled. Possible values: ENABLE (default value), DISABLE.
    subAccountLists List<Number>
    List of numeric identifiers of sub accounts of this account for which the parent account will receive notifications. Should be set if the policy_type is SUB_ACCOUNT.
    subCategory String
    The sub category of notifications that the policy will apply to. The possible values are available via the API at https://api.imperva.com/notification-settings/v3/subtypes.

    Supporting Types

    NotificationCenterPolicyAsset, NotificationCenterPolicyAssetArgs

    AssetType string
    Indicates the Imperva-protected entity that triggers the notification. Possible values: SITE, IP_RANGE, EDGE_IP, ORIGIN_CONNECTIVITY, NETFLOW_EXPORTER, DOMAIN.
    AssetId double
    Numeric identifier of the asset.
    AssetType string
    Indicates the Imperva-protected entity that triggers the notification. Possible values: SITE, IP_RANGE, EDGE_IP, ORIGIN_CONNECTIVITY, NETFLOW_EXPORTER, DOMAIN.
    AssetId float64
    Numeric identifier of the asset.
    assetType String
    Indicates the Imperva-protected entity that triggers the notification. Possible values: SITE, IP_RANGE, EDGE_IP, ORIGIN_CONNECTIVITY, NETFLOW_EXPORTER, DOMAIN.
    assetId Double
    Numeric identifier of the asset.
    assetType string
    Indicates the Imperva-protected entity that triggers the notification. Possible values: SITE, IP_RANGE, EDGE_IP, ORIGIN_CONNECTIVITY, NETFLOW_EXPORTER, DOMAIN.
    assetId number
    Numeric identifier of the asset.
    asset_type str
    Indicates the Imperva-protected entity that triggers the notification. Possible values: SITE, IP_RANGE, EDGE_IP, ORIGIN_CONNECTIVITY, NETFLOW_EXPORTER, DOMAIN.
    asset_id float
    Numeric identifier of the asset.
    assetType String
    Indicates the Imperva-protected entity that triggers the notification. Possible values: SITE, IP_RANGE, EDGE_IP, ORIGIN_CONNECTIVITY, NETFLOW_EXPORTER, DOMAIN.
    assetId Number
    Numeric identifier of the asset.

    Import

    Notification Policy can be imported using the account_id/policy_id

    $ pulumi import incapsula:index/notificationCenterPolicy:NotificationCenterPolicy notification-policy-account-without-assets 12345/9999

    To learn more about importing existing cloud resources, see Importing resources.

    Package Details

    Repository
    incapsula imperva/terraform-provider-incapsula
    License
    Notes
    This Pulumi package is based on the incapsula Terraform Provider.
    incapsula logo
    incapsula 3.33.0 published on Wednesday, Apr 30, 2025 by imperva
    imperva/terraform-provider-incapsula