azurerm_data_factory_trigger_custom_event: Allow subject_begins_wit…

…h and subject_ends_with to both not be set (#25932) * #25929 azurerm_data_factory_trigger_custom_event requires a non-empty string for subject_begins_with or subject_ends_with when the Azure UI does not * #25929
hashicorp · May 14, 2024 · 849f0b4 · 849f0b4
1 parent 5a9b9f1
commit 849f0b4
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 4 deletions.
diff --git a/internal/services/datafactory/data_factory_trigger_custom_event_resource.go b/internal/services/datafactory/data_factory_trigger_custom_event_resource.go
@@ -125,14 +125,12 @@ func resourceDataFactoryTriggerCustomEvent() *pluginsdk.Resource {
 				Type:         pluginsdk.TypeString,
 				Optional:     true,
 				ValidateFunc: validation.StringIsNotEmpty,
-				AtLeastOneOf: []string{"subject_begins_with", "subject_ends_with"},
 			},
 
 			"subject_ends_with": {
 				Type:         pluginsdk.TypeString,
 				Optional:     true,
 				ValidateFunc: validation.StringIsNotEmpty,
-				AtLeastOneOf: []string{"subject_begins_with", "subject_ends_with"},
 			},
 		},
 	}

diff --git a/website/docs/r/data_factory_trigger_custom_event.html.markdown b/website/docs/r/data_factory_trigger_custom_event.html.markdown
@@ -86,8 +86,6 @@ The following arguments are supported:
 
 * `subject_ends_with` - (Optional) The pattern that event subject ends with for trigger to fire.
 
-~> **Note:** At least one of `subject_begins_with` and `subject_ends_with` must be set.
-
 ---
 
 A `pipeline` block supports the following: