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
+16-36Lines changed: 16 additions & 36 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. Settable only for `dns` rules.
112
+
apply to HTTP or network policies.
113
113
114
114
filters: Specify the protocol or layer to evaluate the traffic, identity, and device
115
115
posture expressions.
@@ -125,15 +125,10 @@ 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. 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.
128
+
rule_settings: Set settings related to this rule.
134
129
135
-
schedule: Defines the schedule for activating DNS policies. Settable only for `dns` and
136
-
`dns_resolver` rules.
130
+
schedule: Defines the schedule for activating DNS policies. (HTTP/Egress or L4
131
+
unsupported).
137
132
138
133
traffic: Specify the wirefilter expression used for traffic matching. The API
139
134
automatically formats and sanitizes expressions before storing them. To prevent
@@ -242,7 +237,7 @@ def update(
242
237
243
238
expiration: Defines the expiration time stamp and default duration of a DNS policy. Takes
244
239
precedence over the policy's `schedule` configuration, if any. This does not
245
-
apply to HTTP or network policies. Settable only for `dns` rules.
240
+
apply to HTTP or network policies.
246
241
247
242
filters: Specify the protocol or layer to evaluate the traffic, identity, and device
248
243
posture expressions.
@@ -258,15 +253,10 @@ def update(
258
253
[Order of enforcement](http://developers.cloudflare.com/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement/#manage-precedence-with-terraform)
259
254
to manage precedence via Terraform.
260
255
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.
256
+
rule_settings: Set settings related to this rule.
267
257
268
-
schedule: Defines the schedule for activating DNS policies. Settable only for `dns` and
269
-
`dns_resolver` rules.
258
+
schedule: Defines the schedule for activating DNS policies. (HTTP/Egress or L4
259
+
unsupported).
270
260
271
261
traffic: Specify the wirefilter expression used for traffic matching. The API
272
262
automatically formats and sanitizes expressions before storing them. To prevent
@@ -557,7 +547,7 @@ async def create(
557
547
558
548
expiration: Defines the expiration time stamp and default duration of a DNS policy. Takes
559
549
precedence over the policy's `schedule` configuration, if any. This does not
560
-
apply to HTTP or network policies. Settable only for `dns` rules.
550
+
apply to HTTP or network policies.
561
551
562
552
filters: Specify the protocol or layer to evaluate the traffic, identity, and device
563
553
posture expressions.
@@ -573,15 +563,10 @@ async def create(
573
563
[Order of enforcement](http://developers.cloudflare.com/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement/#manage-precedence-with-terraform)
574
564
to manage precedence via Terraform.
575
565
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.
566
+
rule_settings: Set settings related to this rule.
582
567
583
-
schedule: Defines the schedule for activating DNS policies. Settable only for `dns` and
584
-
`dns_resolver` rules.
568
+
schedule: Defines the schedule for activating DNS policies. (HTTP/Egress or L4
569
+
unsupported).
585
570
586
571
traffic: Specify the wirefilter expression used for traffic matching. The API
587
572
automatically formats and sanitizes expressions before storing them. To prevent
@@ -690,7 +675,7 @@ async def update(
690
675
691
676
expiration: Defines the expiration time stamp and default duration of a DNS policy. Takes
692
677
precedence over the policy's `schedule` configuration, if any. This does not
693
-
apply to HTTP or network policies. Settable only for `dns` rules.
678
+
apply to HTTP or network policies.
694
679
695
680
filters: Specify the protocol or layer to evaluate the traffic, identity, and device
696
681
posture expressions.
@@ -706,15 +691,10 @@ async def update(
706
691
[Order of enforcement](http://developers.cloudflare.com/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement/#manage-precedence-with-terraform)
707
692
to manage precedence via Terraform.
708
693
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.
694
+
rule_settings: Set settings related to this rule.
715
695
716
-
schedule: Defines the schedule for activating DNS policies. Settable only for `dns` and
717
-
`dns_resolver` rules.
696
+
schedule: Defines the schedule for activating DNS policies. (HTTP/Egress or L4
697
+
unsupported).
718
698
719
699
traffic: Specify the wirefilter expression used for traffic matching. The API
720
700
automatically formats and sanitizes expressions before storing them. To prevent
0 commit comments