Skip to content

Commit 7866f94

Browse files
stainless-app[bot]stainless-app[bot]
committed
chore(api): update composite API spec
1 parent 196fc7e commit 7866f94

8 files changed

Lines changed: 262 additions & 82 deletions

File tree

‎.stats.yml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
configured_endpoints: 1826
2-
openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/cloudflare%2Fcloudflare-436dae5b63cd3641097063829d648648b983691f35bac8d179d970741190e128.yml
3-
openapi_spec_hash: 44627cc45ee6623f37d3b9619b124ea5
2+
openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/cloudflare%2Fcloudflare-72ce892ddf4f0cfe8ab511c2f84e4f8612d839ba17e981262ccc0e29c7c4c5df.yml
3+
openapi_spec_hash: e93d4fcda4bcd5ec1a77ddb5782ffd78
44
config_hash: 59212900ef3970ac3c41ca2537fabe7b

‎src/cloudflare/resources/dns_firewall/dns_firewall.py‎

Lines changed: 104 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -114,16 +114,34 @@ def create(
114114
115115
ecs_fallback: Whether to forward client IP (resolver) subnet if no EDNS Client Subnet is sent
116116
117-
maximum_cache_ttl: Maximum DNS cache TTL This setting sets an upper bound on DNS TTLs for purposes
118-
of caching between DNS Firewall and the upstream servers. Higher TTLs will be
119-
decreased to the maximum defined here for caching purposes.
117+
maximum_cache_ttl: By default, Cloudflare attempts to cache responses for as long as indicated by
118+
the TTL received from upstream nameservers. This setting sets an upper bound on
119+
this duration. For caching purposes, higher TTLs will be decreased to the
120+
maximum value defined by this setting.
120121
121-
minimum_cache_ttl: Minimum DNS cache TTL This setting sets a lower bound on DNS TTLs for purposes
122-
of caching between DNS Firewall and the upstream servers. Lower TTLs will be
123-
increased to the minimum defined here for caching purposes.
122+
This setting does not affect the TTL value in the DNS response Cloudflare
123+
returns to clients. Cloudflare will always forward the TTL value received from
124+
upstream nameservers.
124125
125-
negative_cache_ttl: Negative DNS cache TTL This setting controls how long DNS Firewall should cache
126-
negative responses (e.g., NXDOMAIN) from the upstream servers.
126+
minimum_cache_ttl: By default, Cloudflare attempts to cache responses for as long as indicated by
127+
the TTL received from upstream nameservers. This setting sets a lower bound on
128+
this duration. For caching purposes, lower TTLs will be increased to the minimum
129+
value defined by this setting.
130+
131+
This setting does not affect the TTL value in the DNS response Cloudflare
132+
returns to clients. Cloudflare will always forward the TTL value received from
133+
upstream nameservers.
134+
135+
Note that, even with this setting, there is no guarantee that a response will be
136+
cached for at least the specified duration. Cached responses may be removed
137+
earlier for capacity or other operational reasons.
138+
139+
negative_cache_ttl: This setting controls how long DNS Firewall should cache negative responses
140+
(e.g., NXDOMAIN) from the upstream servers.
141+
142+
This setting does not affect the TTL value in the DNS response Cloudflare
143+
returns to clients. Cloudflare will always forward the TTL value received from
144+
upstream nameservers.
127145
128146
ratelimit: Ratelimit in queries per second per datacenter (applies to DNS queries sent to
129147
the upstream nameservers configured on the cluster)
@@ -300,18 +318,36 @@ def edit(
300318
301319
ecs_fallback: Whether to forward client IP (resolver) subnet if no EDNS Client Subnet is sent
302320
303-
maximum_cache_ttl: Maximum DNS cache TTL This setting sets an upper bound on DNS TTLs for purposes
304-
of caching between DNS Firewall and the upstream servers. Higher TTLs will be
305-
decreased to the maximum defined here for caching purposes.
321+
maximum_cache_ttl: By default, Cloudflare attempts to cache responses for as long as indicated by
322+
the TTL received from upstream nameservers. This setting sets an upper bound on
323+
this duration. For caching purposes, higher TTLs will be decreased to the
324+
maximum value defined by this setting.
306325
307-
minimum_cache_ttl: Minimum DNS cache TTL This setting sets a lower bound on DNS TTLs for purposes
308-
of caching between DNS Firewall and the upstream servers. Lower TTLs will be
309-
increased to the minimum defined here for caching purposes.
326+
This setting does not affect the TTL value in the DNS response Cloudflare
327+
returns to clients. Cloudflare will always forward the TTL value received from
328+
upstream nameservers.
329+
330+
minimum_cache_ttl: By default, Cloudflare attempts to cache responses for as long as indicated by
331+
the TTL received from upstream nameservers. This setting sets a lower bound on
332+
this duration. For caching purposes, lower TTLs will be increased to the minimum
333+
value defined by this setting.
334+
335+
This setting does not affect the TTL value in the DNS response Cloudflare
336+
returns to clients. Cloudflare will always forward the TTL value received from
337+
upstream nameservers.
338+
339+
Note that, even with this setting, there is no guarantee that a response will be
340+
cached for at least the specified duration. Cached responses may be removed
341+
earlier for capacity or other operational reasons.
310342
311343
name: DNS Firewall cluster name
312344
313-
negative_cache_ttl: Negative DNS cache TTL This setting controls how long DNS Firewall should cache
314-
negative responses (e.g., NXDOMAIN) from the upstream servers.
345+
negative_cache_ttl: This setting controls how long DNS Firewall should cache negative responses
346+
(e.g., NXDOMAIN) from the upstream servers.
347+
348+
This setting does not affect the TTL value in the DNS response Cloudflare
349+
returns to clients. Cloudflare will always forward the TTL value received from
350+
upstream nameservers.
315351
316352
ratelimit: Ratelimit in queries per second per datacenter (applies to DNS queries sent to
317353
the upstream nameservers configured on the cluster)
@@ -466,16 +502,34 @@ async def create(
466502
467503
ecs_fallback: Whether to forward client IP (resolver) subnet if no EDNS Client Subnet is sent
468504
469-
maximum_cache_ttl: Maximum DNS cache TTL This setting sets an upper bound on DNS TTLs for purposes
470-
of caching between DNS Firewall and the upstream servers. Higher TTLs will be
471-
decreased to the maximum defined here for caching purposes.
505+
maximum_cache_ttl: By default, Cloudflare attempts to cache responses for as long as indicated by
506+
the TTL received from upstream nameservers. This setting sets an upper bound on
507+
this duration. For caching purposes, higher TTLs will be decreased to the
508+
maximum value defined by this setting.
472509
473-
minimum_cache_ttl: Minimum DNS cache TTL This setting sets a lower bound on DNS TTLs for purposes
474-
of caching between DNS Firewall and the upstream servers. Lower TTLs will be
475-
increased to the minimum defined here for caching purposes.
510+
This setting does not affect the TTL value in the DNS response Cloudflare
511+
returns to clients. Cloudflare will always forward the TTL value received from
512+
upstream nameservers.
476513
477-
negative_cache_ttl: Negative DNS cache TTL This setting controls how long DNS Firewall should cache
478-
negative responses (e.g., NXDOMAIN) from the upstream servers.
514+
minimum_cache_ttl: By default, Cloudflare attempts to cache responses for as long as indicated by
515+
the TTL received from upstream nameservers. This setting sets a lower bound on
516+
this duration. For caching purposes, lower TTLs will be increased to the minimum
517+
value defined by this setting.
518+
519+
This setting does not affect the TTL value in the DNS response Cloudflare
520+
returns to clients. Cloudflare will always forward the TTL value received from
521+
upstream nameservers.
522+
523+
Note that, even with this setting, there is no guarantee that a response will be
524+
cached for at least the specified duration. Cached responses may be removed
525+
earlier for capacity or other operational reasons.
526+
527+
negative_cache_ttl: This setting controls how long DNS Firewall should cache negative responses
528+
(e.g., NXDOMAIN) from the upstream servers.
529+
530+
This setting does not affect the TTL value in the DNS response Cloudflare
531+
returns to clients. Cloudflare will always forward the TTL value received from
532+
upstream nameservers.
479533
480534
ratelimit: Ratelimit in queries per second per datacenter (applies to DNS queries sent to
481535
the upstream nameservers configured on the cluster)
@@ -652,18 +706,36 @@ async def edit(
652706
653707
ecs_fallback: Whether to forward client IP (resolver) subnet if no EDNS Client Subnet is sent
654708
655-
maximum_cache_ttl: Maximum DNS cache TTL This setting sets an upper bound on DNS TTLs for purposes
656-
of caching between DNS Firewall and the upstream servers. Higher TTLs will be
657-
decreased to the maximum defined here for caching purposes.
709+
maximum_cache_ttl: By default, Cloudflare attempts to cache responses for as long as indicated by
710+
the TTL received from upstream nameservers. This setting sets an upper bound on
711+
this duration. For caching purposes, higher TTLs will be decreased to the
712+
maximum value defined by this setting.
658713
659-
minimum_cache_ttl: Minimum DNS cache TTL This setting sets a lower bound on DNS TTLs for purposes
660-
of caching between DNS Firewall and the upstream servers. Lower TTLs will be
661-
increased to the minimum defined here for caching purposes.
714+
This setting does not affect the TTL value in the DNS response Cloudflare
715+
returns to clients. Cloudflare will always forward the TTL value received from
716+
upstream nameservers.
717+
718+
minimum_cache_ttl: By default, Cloudflare attempts to cache responses for as long as indicated by
719+
the TTL received from upstream nameservers. This setting sets a lower bound on
720+
this duration. For caching purposes, lower TTLs will be increased to the minimum
721+
value defined by this setting.
722+
723+
This setting does not affect the TTL value in the DNS response Cloudflare
724+
returns to clients. Cloudflare will always forward the TTL value received from
725+
upstream nameservers.
726+
727+
Note that, even with this setting, there is no guarantee that a response will be
728+
cached for at least the specified duration. Cached responses may be removed
729+
earlier for capacity or other operational reasons.
662730
663731
name: DNS Firewall cluster name
664732
665-
negative_cache_ttl: Negative DNS cache TTL This setting controls how long DNS Firewall should cache
666-
negative responses (e.g., NXDOMAIN) from the upstream servers.
733+
negative_cache_ttl: This setting controls how long DNS Firewall should cache negative responses
734+
(e.g., NXDOMAIN) from the upstream servers.
735+
736+
This setting does not affect the TTL value in the DNS response Cloudflare
737+
returns to clients. Cloudflare will always forward the TTL value received from
738+
upstream nameservers.
667739
668740
ratelimit: Ratelimit in queries per second per datacenter (applies to DNS queries sent to
669741
the upstream nameservers configured on the cluster)

‎src/cloudflare/types/dns_firewall/dns_firewall_create_params.py‎

Lines changed: 26 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -32,22 +32,40 @@ class DNSFirewallCreateParams(TypedDict, total=False):
3232

3333
maximum_cache_ttl: float
3434
"""
35-
Maximum DNS cache TTL This setting sets an upper bound on DNS TTLs for purposes
36-
of caching between DNS Firewall and the upstream servers. Higher TTLs will be
37-
decreased to the maximum defined here for caching purposes.
35+
By default, Cloudflare attempts to cache responses for as long as indicated by
36+
the TTL received from upstream nameservers. This setting sets an upper bound on
37+
this duration. For caching purposes, higher TTLs will be decreased to the
38+
maximum value defined by this setting.
39+
40+
This setting does not affect the TTL value in the DNS response Cloudflare
41+
returns to clients. Cloudflare will always forward the TTL value received from
42+
upstream nameservers.
3843
"""
3944

4045
minimum_cache_ttl: float
4146
"""
42-
Minimum DNS cache TTL This setting sets a lower bound on DNS TTLs for purposes
43-
of caching between DNS Firewall and the upstream servers. Lower TTLs will be
44-
increased to the minimum defined here for caching purposes.
47+
By default, Cloudflare attempts to cache responses for as long as indicated by
48+
the TTL received from upstream nameservers. This setting sets a lower bound on
49+
this duration. For caching purposes, lower TTLs will be increased to the minimum
50+
value defined by this setting.
51+
52+
This setting does not affect the TTL value in the DNS response Cloudflare
53+
returns to clients. Cloudflare will always forward the TTL value received from
54+
upstream nameservers.
55+
56+
Note that, even with this setting, there is no guarantee that a response will be
57+
cached for at least the specified duration. Cached responses may be removed
58+
earlier for capacity or other operational reasons.
4559
"""
4660

4761
negative_cache_ttl: Optional[float]
4862
"""
49-
Negative DNS cache TTL This setting controls how long DNS Firewall should cache
50-
negative responses (e.g., NXDOMAIN) from the upstream servers.
63+
This setting controls how long DNS Firewall should cache negative responses
64+
(e.g., NXDOMAIN) from the upstream servers.
65+
66+
This setting does not affect the TTL value in the DNS response Cloudflare
67+
returns to clients. Cloudflare will always forward the TTL value received from
68+
upstream nameservers.
5169
"""
5270

5371
ratelimit: Optional[float]

‎src/cloudflare/types/dns_firewall/dns_firewall_create_response.py‎

Lines changed: 26 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -25,16 +25,30 @@ class DNSFirewallCreateResponse(BaseModel):
2525

2626
maximum_cache_ttl: float
2727
"""
28-
Maximum DNS cache TTL This setting sets an upper bound on DNS TTLs for purposes
29-
of caching between DNS Firewall and the upstream servers. Higher TTLs will be
30-
decreased to the maximum defined here for caching purposes.
28+
By default, Cloudflare attempts to cache responses for as long as indicated by
29+
the TTL received from upstream nameservers. This setting sets an upper bound on
30+
this duration. For caching purposes, higher TTLs will be decreased to the
31+
maximum value defined by this setting.
32+
33+
This setting does not affect the TTL value in the DNS response Cloudflare
34+
returns to clients. Cloudflare will always forward the TTL value received from
35+
upstream nameservers.
3136
"""
3237

3338
minimum_cache_ttl: float
3439
"""
35-
Minimum DNS cache TTL This setting sets a lower bound on DNS TTLs for purposes
36-
of caching between DNS Firewall and the upstream servers. Lower TTLs will be
37-
increased to the minimum defined here for caching purposes.
40+
By default, Cloudflare attempts to cache responses for as long as indicated by
41+
the TTL received from upstream nameservers. This setting sets a lower bound on
42+
this duration. For caching purposes, lower TTLs will be increased to the minimum
43+
value defined by this setting.
44+
45+
This setting does not affect the TTL value in the DNS response Cloudflare
46+
returns to clients. Cloudflare will always forward the TTL value received from
47+
upstream nameservers.
48+
49+
Note that, even with this setting, there is no guarantee that a response will be
50+
cached for at least the specified duration. Cached responses may be removed
51+
earlier for capacity or other operational reasons.
3852
"""
3953

4054
modified_on: datetime
@@ -45,8 +59,12 @@ class DNSFirewallCreateResponse(BaseModel):
4559

4660
negative_cache_ttl: Optional[float] = None
4761
"""
48-
Negative DNS cache TTL This setting controls how long DNS Firewall should cache
49-
negative responses (e.g., NXDOMAIN) from the upstream servers.
62+
This setting controls how long DNS Firewall should cache negative responses
63+
(e.g., NXDOMAIN) from the upstream servers.
64+
65+
This setting does not affect the TTL value in the DNS response Cloudflare
66+
returns to clients. Cloudflare will always forward the TTL value received from
67+
upstream nameservers.
5068
"""
5169

5270
ratelimit: Optional[float] = None

‎src/cloudflare/types/dns_firewall/dns_firewall_edit_params.py‎

Lines changed: 26 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -27,25 +27,43 @@ class DNSFirewallEditParams(TypedDict, total=False):
2727

2828
maximum_cache_ttl: float
2929
"""
30-
Maximum DNS cache TTL This setting sets an upper bound on DNS TTLs for purposes
31-
of caching between DNS Firewall and the upstream servers. Higher TTLs will be
32-
decreased to the maximum defined here for caching purposes.
30+
By default, Cloudflare attempts to cache responses for as long as indicated by
31+
the TTL received from upstream nameservers. This setting sets an upper bound on
32+
this duration. For caching purposes, higher TTLs will be decreased to the
33+
maximum value defined by this setting.
34+
35+
This setting does not affect the TTL value in the DNS response Cloudflare
36+
returns to clients. Cloudflare will always forward the TTL value received from
37+
upstream nameservers.
3338
"""
3439

3540
minimum_cache_ttl: float
3641
"""
37-
Minimum DNS cache TTL This setting sets a lower bound on DNS TTLs for purposes
38-
of caching between DNS Firewall and the upstream servers. Lower TTLs will be
39-
increased to the minimum defined here for caching purposes.
42+
By default, Cloudflare attempts to cache responses for as long as indicated by
43+
the TTL received from upstream nameservers. This setting sets a lower bound on
44+
this duration. For caching purposes, lower TTLs will be increased to the minimum
45+
value defined by this setting.
46+
47+
This setting does not affect the TTL value in the DNS response Cloudflare
48+
returns to clients. Cloudflare will always forward the TTL value received from
49+
upstream nameservers.
50+
51+
Note that, even with this setting, there is no guarantee that a response will be
52+
cached for at least the specified duration. Cached responses may be removed
53+
earlier for capacity or other operational reasons.
4054
"""
4155

4256
name: str
4357
"""DNS Firewall cluster name"""
4458

4559
negative_cache_ttl: Optional[float]
4660
"""
47-
Negative DNS cache TTL This setting controls how long DNS Firewall should cache
48-
negative responses (e.g., NXDOMAIN) from the upstream servers.
61+
This setting controls how long DNS Firewall should cache negative responses
62+
(e.g., NXDOMAIN) from the upstream servers.
63+
64+
This setting does not affect the TTL value in the DNS response Cloudflare
65+
returns to clients. Cloudflare will always forward the TTL value received from
66+
upstream nameservers.
4967
"""
5068

5169
ratelimit: Optional[float]

0 commit comments

Comments
 (0)