add note for not supported attributes (#215)

Author: BrachaY

website/docs/r/api_security_api_config.html.markdown

@@ -44,6 +44,9 @@ The following arguments are supported:
   values:
   `ALERT_ONLY`, `BLOCK_REQUEST`, `BLOCK_USER`, `BLOCK_IP`, `IGNORE`,`DEFAULT`. Assigning `DEFAULT` will inherit the
   action from parent object.
+  
+  > **NOTE:** `invalid_param_name_violation_action` parameter is currently not supported. Please do not use/change value.
+
 * `invalid_param_value_violation_action` - (Optional) The action taken when an invalid parameter value Violation occurs.
   Assigning `DEFAULT` will inherit the action from parent object. Possible values: `ALERT_ONLY`, `BLOCK_REQUEST`
   , `BLOCK_USER`, `BLOCK_IP`, `IGNORE`,`DEFAULT`. Assigning `DEFAULT` will inherit the action from parent object.

website/docs/r/api_security_endpoint_config.html.markdown

@@ -34,6 +34,10 @@ The following arguments are supported:
 * `invalid_param_value_violation_action` - (Optional) The action taken when an invalid parameter value Violation occurs.
   Possible values: `ALERT_ONLY`, `BLOCK_REQUEST`, `BLOCK_USER`, `BLOCK_IP`, `IGNORE`, `DEFAULT`. Assigning `DEFAULT`
   will inherit the action from parent object.
+  
+  > **NOTE:** `invalid_param_name_violation_action` parameter is currently not supported. Please do not use/change value.
+
+  
 * `invalid_param_name_violation_action` - (Optional) The action taken when an invalid parameter value Violation occurs.
   Possible values: `ALERT_ONLY`, `BLOCK_REQUEST`, `BLOCK_USER`, `BLOCK_IP`, `IGNORE`, `DEFAULT`. Assigning `DEFAULT`
   will inherit the action from parent object.

website/docs/r/api_security_site_config.html.markdown

@@ -42,6 +42,9 @@ The following arguments are supported:
   Possible values: `ALERT_ONLY` (default value), `BLOCK_REQUEST`, `BLOCK_USER`, `BLOCK_IP`, `IGNORE`.
 * `invalid_param_name_violation_action` - (Optional) The action taken when an invalid parameter value Violation occurs.
   Possible values: `ALERT_ONLY` (default value), `BLOCK_REQUEST`, `BLOCK_USER`, `BLOCK_IP`, `IGNORE`.
+  
+  > **NOTE:** `invalid_param_name_violation_action` parameter is currently not supported. Please do not use/change value.
+  
 * `is_api_only_site` - (Optional) Apply positive security model for all traffic on the site. Applying the positive
   security model for all traffic on the site may lead to undesired request blocking.
 * `non_api_request_violation_action` - (Optional) Action to be taken for traffic on the site that does not target the

website/docs/r/site.html.markdown

@@ -62,6 +62,9 @@ The following arguments are supported:
 * `force_ssl` - (Optional) Force SSL. This option is only available for sites with manually configured IP/CNAME and for specific accounts.
 * `logs_account_id` - (Optional) Account where logs should be stored. Available only for Enterprise Plan customers that purchased the Logs Integration SKU. Numeric identifier of the account that purchased the logs integration SKU and which collects the logs. If not specified, operation will be performed on the account identified by the authentication parameters.
 * `active` - (Optional) Whether the site is active or bypassed by the Imperva network. Options are `active` and `bypass`.
+ 
+  > **NOTE:** `restricted_cname_reuse` parameter is currently not supported. Please do not use/change value.
+
 * `restricted_cname_reuse` - (Optional) Use this option to allow Imperva to detect and add domains that are using the Imperva-provided CNAME (not recommended). One of: true | false.
 * `domain_validation` - (Optional) Sets the domain validation method that will be used to generate an SSL certificate. Options are `email`, `html`, `cname` and `dns`.
 * `approver` - (Optional) Sets the approver e-mail address that will be used to perform SSL domain validation.