You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/cloudflare/resources/zero_trust/gateway/rules.py
+36-16Lines changed: 36 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,7 @@ def create(
109
109
110
110
expiration: Defines the expiration time stamp and default duration of a DNS policy. Takes
111
111
precedence over the policy's `schedule` configuration, if any. This does not
112
-
apply to HTTP or network policies.
112
+
apply to HTTP or network policies. Settable only for `dns` rules.
113
113
114
114
filters: Specify the protocol or layer to evaluate the traffic, identity, and device
115
115
posture expressions.
@@ -125,10 +125,15 @@ def create(
125
125
[Order of enforcement](http://developers.cloudflare.com/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement/#manage-precedence-with-terraform)
126
126
to manage precedence via Terraform.
127
127
128
-
rule_settings: Set settings related to this rule.
128
+
rule_settings: Set settings related to this rule. Each setting is only valid for specific rule
129
+
types and can only be used with the appropriate selectors. If Terraform drift is
130
+
observed in these setting values, verify that the setting is supported for the
131
+
given rule type and that the API response reflects the requested value. If the
132
+
API response returns sanitized or modified values that differ from the request,
133
+
use the API-provided values in Terraform to ensure consistency.
129
134
130
-
schedule: Defines the schedule for activating DNS policies. (HTTP/Egress or L4
131
-
unsupported).
135
+
schedule: Defines the schedule for activating DNS policies. Settable only for `dns` and
136
+
`dns_resolver` rules.
132
137
133
138
traffic: Specify the wirefilter expression used for traffic matching. The API
134
139
automatically formats and sanitizes expressions before storing them. To prevent
@@ -237,7 +242,7 @@ def update(
237
242
238
243
expiration: Defines the expiration time stamp and default duration of a DNS policy. Takes
239
244
precedence over the policy's `schedule` configuration, if any. This does not
240
-
apply to HTTP or network policies.
245
+
apply to HTTP or network policies. Settable only for `dns` rules.
241
246
242
247
filters: Specify the protocol or layer to evaluate the traffic, identity, and device
243
248
posture expressions.
@@ -253,10 +258,15 @@ def update(
253
258
[Order of enforcement](http://developers.cloudflare.com/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement/#manage-precedence-with-terraform)
254
259
to manage precedence via Terraform.
255
260
256
-
rule_settings: Set settings related to this rule.
261
+
rule_settings: Set settings related to this rule. Each setting is only valid for specific rule
262
+
types and can only be used with the appropriate selectors. If Terraform drift is
263
+
observed in these setting values, verify that the setting is supported for the
264
+
given rule type and that the API response reflects the requested value. If the
265
+
API response returns sanitized or modified values that differ from the request,
266
+
use the API-provided values in Terraform to ensure consistency.
257
267
258
-
schedule: Defines the schedule for activating DNS policies. (HTTP/Egress or L4
259
-
unsupported).
268
+
schedule: Defines the schedule for activating DNS policies. Settable only for `dns` and
269
+
`dns_resolver` rules.
260
270
261
271
traffic: Specify the wirefilter expression used for traffic matching. The API
262
272
automatically formats and sanitizes expressions before storing them. To prevent
@@ -547,7 +557,7 @@ async def create(
547
557
548
558
expiration: Defines the expiration time stamp and default duration of a DNS policy. Takes
549
559
precedence over the policy's `schedule` configuration, if any. This does not
550
-
apply to HTTP or network policies.
560
+
apply to HTTP or network policies. Settable only for `dns` rules.
551
561
552
562
filters: Specify the protocol or layer to evaluate the traffic, identity, and device
553
563
posture expressions.
@@ -563,10 +573,15 @@ async def create(
563
573
[Order of enforcement](http://developers.cloudflare.com/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement/#manage-precedence-with-terraform)
564
574
to manage precedence via Terraform.
565
575
566
-
rule_settings: Set settings related to this rule.
576
+
rule_settings: Set settings related to this rule. Each setting is only valid for specific rule
577
+
types and can only be used with the appropriate selectors. If Terraform drift is
578
+
observed in these setting values, verify that the setting is supported for the
579
+
given rule type and that the API response reflects the requested value. If the
580
+
API response returns sanitized or modified values that differ from the request,
581
+
use the API-provided values in Terraform to ensure consistency.
567
582
568
-
schedule: Defines the schedule for activating DNS policies. (HTTP/Egress or L4
569
-
unsupported).
583
+
schedule: Defines the schedule for activating DNS policies. Settable only for `dns` and
584
+
`dns_resolver` rules.
570
585
571
586
traffic: Specify the wirefilter expression used for traffic matching. The API
572
587
automatically formats and sanitizes expressions before storing them. To prevent
@@ -675,7 +690,7 @@ async def update(
675
690
676
691
expiration: Defines the expiration time stamp and default duration of a DNS policy. Takes
677
692
precedence over the policy's `schedule` configuration, if any. This does not
678
-
apply to HTTP or network policies.
693
+
apply to HTTP or network policies. Settable only for `dns` rules.
679
694
680
695
filters: Specify the protocol or layer to evaluate the traffic, identity, and device
681
696
posture expressions.
@@ -691,10 +706,15 @@ async def update(
691
706
[Order of enforcement](http://developers.cloudflare.com/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement/#manage-precedence-with-terraform)
692
707
to manage precedence via Terraform.
693
708
694
-
rule_settings: Set settings related to this rule.
709
+
rule_settings: Set settings related to this rule. Each setting is only valid for specific rule
710
+
types and can only be used with the appropriate selectors. If Terraform drift is
711
+
observed in these setting values, verify that the setting is supported for the
712
+
given rule type and that the API response reflects the requested value. If the
713
+
API response returns sanitized or modified values that differ from the request,
714
+
use the API-provided values in Terraform to ensure consistency.
695
715
696
-
schedule: Defines the schedule for activating DNS policies. (HTTP/Egress or L4
697
-
unsupported).
716
+
schedule: Defines the schedule for activating DNS policies. Settable only for `dns` and
717
+
`dns_resolver` rules.
698
718
699
719
traffic: Specify the wirefilter expression used for traffic matching. The API
700
720
automatically formats and sanitizes expressions before storing them. To prevent
0 commit comments