cloudflare 4.5.0 → 5.0.0

package/resources/load-balancers/load-balancers.d.ts

@@ -281,7 +281,7 @@ export interface LoadBalancer {
      */
     networks?: Array<string>;
     /**
-     * (Enterprise only): A mapping of Cloudflare PoP identifiers to a list of pool IDs
+     * Enterprise only: A mapping of Cloudflare PoP identifiers to a list of pool IDs
      * (ordered by their failover priority) for the PoP (datacenter). Any PoPs not
      * explicitly defined will fall back to using the corresponding country_pool, then
      * region_pool mapping if it exists else to default_pools.
@@ -319,28 +319,25 @@ export interface LoadBalancer {
     rules?: Array<Rules>;
     /**
      * Specifies the type of session affinity the load balancer should use unless
-     * specified as `"none"`. The supported types are:
-     *
-     * - `"cookie"`: On the first request to a proxied load balancer, a cookie is
-     *   generated, encoding information of which origin the request will be forwarded
-     *   to. Subsequent requests, by the same client to the same load balancer, will be
-     *   sent to the origin server the cookie encodes, for the duration of the cookie
-     *   and as long as the origin server remains healthy. If the cookie has expired or
-     *   the origin server is unhealthy, then a new origin server is calculated and
-     *   used.
-     * - `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
-     *   selection is stable and based on the client's ip address.
-     * - `"header"`: On the first request to a proxied load balancer, a session key
-     *   based on the configured HTTP headers (see
-     *   `session_affinity_attributes.headers`) is generated, encoding the request
-     *   headers used for storing in the load balancer session state which origin the
-     *   request will be forwarded to. Subsequent requests to the load balancer with
-     *   the same headers will be sent to the same origin server, for the duration of
-     *   the session and as long as the origin server remains healthy. If the session
-     *   has been idle for the duration of `session_affinity_ttl` seconds or the origin
-     *   server is unhealthy, then a new origin server is calculated and used. See
-     *   `headers` in `session_affinity_attributes` for additional required
-     *   configuration.
+     * specified as `"none"`. The supported types are: - `"cookie"`: On the first
+     * request to a proxied load balancer, a cookie is generated, encoding information
+     * of which origin the request will be forwarded to. Subsequent requests, by the
+     * same client to the same load balancer, will be sent to the origin server the
+     * cookie encodes, for the duration of the cookie and as long as the origin server
+     * remains healthy. If the cookie has expired or the origin server is unhealthy,
+     * then a new origin server is calculated and used. - `"ip_cookie"`: Behaves the
+     * same as `"cookie"` except the initial origin selection is stable and based on
+     * the client's ip address. - `"header"`: On the first request to a proxied load
+     * balancer, a session key based on the configured HTTP headers (see
+     * `session_affinity_attributes.headers`) is generated, encoding the request
+     * headers used for storing in the load balancer session state which origin the
+     * request will be forwarded to. Subsequent requests to the load balancer with the
+     * same headers will be sent to the same origin server, for the duration of the
+     * session and as long as the origin server remains healthy. If the session has
+     * been idle for the duration of `session_affinity_ttl` seconds or the origin
+     * server is unhealthy, then a new origin server is calculated and used. See
+     * `headers` in `session_affinity_attributes` for additional required
+     * configuration.
      */
     session_affinity?: SessionAffinity;
     /**
@@ -350,14 +347,13 @@ export interface LoadBalancer {
     /**
      * Time, in seconds, until a client's session expires after being created. Once the
      * expiry time has been reached, subsequent requests may get sent to a different
-     * origin server. The accepted ranges per `session_affinity` policy are:
-     *
-     * - `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used
-     *   unless explicitly set. The accepted range of values is between [1800, 604800].
-     * - `"header"`: The current default of 1800 seconds will be used unless explicitly
-     *   set. The accepted range of values is between [30, 3600]. Note: With session
-     *   affinity by header, sessions only expire after they haven't been used for the
-     *   number of seconds specified.
+     * origin server. The accepted ranges per `session_affinity` policy are: -
+     * `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used unless
+     * explicitly set. The accepted range of values is between [1800, 604800]. -
+     * `"header"`: The current default of 1800 seconds will be used unless explicitly
+     * set. The accepted range of values is between [30, 3600]. Note: With session
+     * affinity by header, sessions only expire after they haven't been used for the
+     * number of seconds specified.
      */
     session_affinity_ttl?: number;
     /**
@@ -822,7 +818,7 @@ export declare namespace Rules {
          */
         location_strategy?: LoadBalancersAPI.LocationStrategy;
         /**
-         * (Enterprise only): A mapping of Cloudflare PoP identifiers to a list of pool IDs
+         * Enterprise only: A mapping of Cloudflare PoP identifiers to a list of pool IDs
          * (ordered by their failover priority) for the PoP (datacenter). Any PoPs not
          * explicitly defined will fall back to using the corresponding country_pool, then
          * region_pool mapping if it exists else to default_pools.
@@ -851,28 +847,25 @@ export declare namespace Rules {
         };
         /**
          * Specifies the type of session affinity the load balancer should use unless
-         * specified as `"none"`. The supported types are:
-         *
-         * - `"cookie"`: On the first request to a proxied load balancer, a cookie is
-         *   generated, encoding information of which origin the request will be forwarded
-         *   to. Subsequent requests, by the same client to the same load balancer, will be
-         *   sent to the origin server the cookie encodes, for the duration of the cookie
-         *   and as long as the origin server remains healthy. If the cookie has expired or
-         *   the origin server is unhealthy, then a new origin server is calculated and
-         *   used.
-         * - `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
-         *   selection is stable and based on the client's ip address.
-         * - `"header"`: On the first request to a proxied load balancer, a session key
-         *   based on the configured HTTP headers (see
-         *   `session_affinity_attributes.headers`) is generated, encoding the request
-         *   headers used for storing in the load balancer session state which origin the
-         *   request will be forwarded to. Subsequent requests to the load balancer with
-         *   the same headers will be sent to the same origin server, for the duration of
-         *   the session and as long as the origin server remains healthy. If the session
-         *   has been idle for the duration of `session_affinity_ttl` seconds or the origin
-         *   server is unhealthy, then a new origin server is calculated and used. See
-         *   `headers` in `session_affinity_attributes` for additional required
-         *   configuration.
+         * specified as `"none"`. The supported types are: - `"cookie"`: On the first
+         * request to a proxied load balancer, a cookie is generated, encoding information
+         * of which origin the request will be forwarded to. Subsequent requests, by the
+         * same client to the same load balancer, will be sent to the origin server the
+         * cookie encodes, for the duration of the cookie and as long as the origin server
+         * remains healthy. If the cookie has expired or the origin server is unhealthy,
+         * then a new origin server is calculated and used. - `"ip_cookie"`: Behaves the
+         * same as `"cookie"` except the initial origin selection is stable and based on
+         * the client's ip address. - `"header"`: On the first request to a proxied load
+         * balancer, a session key based on the configured HTTP headers (see
+         * `session_affinity_attributes.headers`) is generated, encoding the request
+         * headers used for storing in the load balancer session state which origin the
+         * request will be forwarded to. Subsequent requests to the load balancer with the
+         * same headers will be sent to the same origin server, for the duration of the
+         * session and as long as the origin server remains healthy. If the session has
+         * been idle for the duration of `session_affinity_ttl` seconds or the origin
+         * server is unhealthy, then a new origin server is calculated and used. See
+         * `headers` in `session_affinity_attributes` for additional required
+         * configuration.
          */
         session_affinity?: LoadBalancersAPI.SessionAffinity;
         /**
@@ -882,14 +875,13 @@ export declare namespace Rules {
         /**
          * Time, in seconds, until a client's session expires after being created. Once the
          * expiry time has been reached, subsequent requests may get sent to a different
-         * origin server. The accepted ranges per `session_affinity` policy are:
-         *
-         * - `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used
-         *   unless explicitly set. The accepted range of values is between [1800, 604800].
-         * - `"header"`: The current default of 1800 seconds will be used unless explicitly
-         *   set. The accepted range of values is between [30, 3600]. Note: With session
-         *   affinity by header, sessions only expire after they haven't been used for the
-         *   number of seconds specified.
+         * origin server. The accepted ranges per `session_affinity` policy are: -
+         * `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used unless
+         * explicitly set. The accepted range of values is between [1800, 604800]. -
+         * `"header"`: The current default of 1800 seconds will be used unless explicitly
+         * set. The accepted range of values is between [30, 3600]. Note: With session
+         * affinity by header, sessions only expire after they haven't been used for the
+         * number of seconds specified.
          */
         session_affinity_ttl?: number;
         /**
@@ -1031,7 +1023,7 @@ export declare namespace RulesParam {
          */
         location_strategy?: LoadBalancersAPI.LocationStrategyParam;
         /**
-         * (Enterprise only): A mapping of Cloudflare PoP identifiers to a list of pool IDs
+         * Enterprise only: A mapping of Cloudflare PoP identifiers to a list of pool IDs
          * (ordered by their failover priority) for the PoP (datacenter). Any PoPs not
          * explicitly defined will fall back to using the corresponding country_pool, then
          * region_pool mapping if it exists else to default_pools.
@@ -1060,28 +1052,25 @@ export declare namespace RulesParam {
         };
         /**
          * Specifies the type of session affinity the load balancer should use unless
-         * specified as `"none"`. The supported types are:
-         *
-         * - `"cookie"`: On the first request to a proxied load balancer, a cookie is
-         *   generated, encoding information of which origin the request will be forwarded
-         *   to. Subsequent requests, by the same client to the same load balancer, will be
-         *   sent to the origin server the cookie encodes, for the duration of the cookie
-         *   and as long as the origin server remains healthy. If the cookie has expired or
-         *   the origin server is unhealthy, then a new origin server is calculated and
-         *   used.
-         * - `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
-         *   selection is stable and based on the client's ip address.
-         * - `"header"`: On the first request to a proxied load balancer, a session key
-         *   based on the configured HTTP headers (see
-         *   `session_affinity_attributes.headers`) is generated, encoding the request
-         *   headers used for storing in the load balancer session state which origin the
-         *   request will be forwarded to. Subsequent requests to the load balancer with
-         *   the same headers will be sent to the same origin server, for the duration of
-         *   the session and as long as the origin server remains healthy. If the session
-         *   has been idle for the duration of `session_affinity_ttl` seconds or the origin
-         *   server is unhealthy, then a new origin server is calculated and used. See
-         *   `headers` in `session_affinity_attributes` for additional required
-         *   configuration.
+         * specified as `"none"`. The supported types are: - `"cookie"`: On the first
+         * request to a proxied load balancer, a cookie is generated, encoding information
+         * of which origin the request will be forwarded to. Subsequent requests, by the
+         * same client to the same load balancer, will be sent to the origin server the
+         * cookie encodes, for the duration of the cookie and as long as the origin server
+         * remains healthy. If the cookie has expired or the origin server is unhealthy,
+         * then a new origin server is calculated and used. - `"ip_cookie"`: Behaves the
+         * same as `"cookie"` except the initial origin selection is stable and based on
+         * the client's ip address. - `"header"`: On the first request to a proxied load
+         * balancer, a session key based on the configured HTTP headers (see
+         * `session_affinity_attributes.headers`) is generated, encoding the request
+         * headers used for storing in the load balancer session state which origin the
+         * request will be forwarded to. Subsequent requests to the load balancer with the
+         * same headers will be sent to the same origin server, for the duration of the
+         * session and as long as the origin server remains healthy. If the session has
+         * been idle for the duration of `session_affinity_ttl` seconds or the origin
+         * server is unhealthy, then a new origin server is calculated and used. See
+         * `headers` in `session_affinity_attributes` for additional required
+         * configuration.
          */
         session_affinity?: LoadBalancersAPI.SessionAffinityParam;
         /**
@@ -1091,14 +1080,13 @@ export declare namespace RulesParam {
         /**
          * Time, in seconds, until a client's session expires after being created. Once the
          * expiry time has been reached, subsequent requests may get sent to a different
-         * origin server. The accepted ranges per `session_affinity` policy are:
-         *
-         * - `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used
-         *   unless explicitly set. The accepted range of values is between [1800, 604800].
-         * - `"header"`: The current default of 1800 seconds will be used unless explicitly
-         *   set. The accepted range of values is between [30, 3600]. Note: With session
-         *   affinity by header, sessions only expire after they haven't been used for the
-         *   number of seconds specified.
+         * origin server. The accepted ranges per `session_affinity` policy are: -
+         * `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used unless
+         * explicitly set. The accepted range of values is between [1800, 604800]. -
+         * `"header"`: The current default of 1800 seconds will be used unless explicitly
+         * set. The accepted range of values is between [30, 3600]. Note: With session
+         * affinity by header, sessions only expire after they haven't been used for the
+         * number of seconds specified.
          */
         session_affinity_ttl?: number;
         /**
@@ -1135,54 +1123,48 @@ export declare namespace RulesParam {
 }
 /**
  * Specifies the type of session affinity the load balancer should use unless
- * specified as `"none"`. The supported types are:
- *
- * - `"cookie"`: On the first request to a proxied load balancer, a cookie is
- *   generated, encoding information of which origin the request will be forwarded
- *   to. Subsequent requests, by the same client to the same load balancer, will be
- *   sent to the origin server the cookie encodes, for the duration of the cookie
- *   and as long as the origin server remains healthy. If the cookie has expired or
- *   the origin server is unhealthy, then a new origin server is calculated and
- *   used.
- * - `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
- *   selection is stable and based on the client's ip address.
- * - `"header"`: On the first request to a proxied load balancer, a session key
- *   based on the configured HTTP headers (see
- *   `session_affinity_attributes.headers`) is generated, encoding the request
- *   headers used for storing in the load balancer session state which origin the
- *   request will be forwarded to. Subsequent requests to the load balancer with
- *   the same headers will be sent to the same origin server, for the duration of
- *   the session and as long as the origin server remains healthy. If the session
- *   has been idle for the duration of `session_affinity_ttl` seconds or the origin
- *   server is unhealthy, then a new origin server is calculated and used. See
- *   `headers` in `session_affinity_attributes` for additional required
- *   configuration.
+ * specified as `"none"`. The supported types are: - `"cookie"`: On the first
+ * request to a proxied load balancer, a cookie is generated, encoding information
+ * of which origin the request will be forwarded to. Subsequent requests, by the
+ * same client to the same load balancer, will be sent to the origin server the
+ * cookie encodes, for the duration of the cookie and as long as the origin server
+ * remains healthy. If the cookie has expired or the origin server is unhealthy,
+ * then a new origin server is calculated and used. - `"ip_cookie"`: Behaves the
+ * same as `"cookie"` except the initial origin selection is stable and based on
+ * the client's ip address. - `"header"`: On the first request to a proxied load
+ * balancer, a session key based on the configured HTTP headers (see
+ * `session_affinity_attributes.headers`) is generated, encoding the request
+ * headers used for storing in the load balancer session state which origin the
+ * request will be forwarded to. Subsequent requests to the load balancer with the
+ * same headers will be sent to the same origin server, for the duration of the
+ * session and as long as the origin server remains healthy. If the session has
+ * been idle for the duration of `session_affinity_ttl` seconds or the origin
+ * server is unhealthy, then a new origin server is calculated and used. See
+ * `headers` in `session_affinity_attributes` for additional required
+ * configuration.
  */
 export type SessionAffinity = 'none' | 'cookie' | 'ip_cookie' | 'header';
 /**
  * Specifies the type of session affinity the load balancer should use unless
- * specified as `"none"`. The supported types are:
- *
- * - `"cookie"`: On the first request to a proxied load balancer, a cookie is
- *   generated, encoding information of which origin the request will be forwarded
- *   to. Subsequent requests, by the same client to the same load balancer, will be
- *   sent to the origin server the cookie encodes, for the duration of the cookie
- *   and as long as the origin server remains healthy. If the cookie has expired or
- *   the origin server is unhealthy, then a new origin server is calculated and
- *   used.
- * - `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
- *   selection is stable and based on the client's ip address.
- * - `"header"`: On the first request to a proxied load balancer, a session key
- *   based on the configured HTTP headers (see
- *   `session_affinity_attributes.headers`) is generated, encoding the request
- *   headers used for storing in the load balancer session state which origin the
- *   request will be forwarded to. Subsequent requests to the load balancer with
- *   the same headers will be sent to the same origin server, for the duration of
- *   the session and as long as the origin server remains healthy. If the session
- *   has been idle for the duration of `session_affinity_ttl` seconds or the origin
- *   server is unhealthy, then a new origin server is calculated and used. See
- *   `headers` in `session_affinity_attributes` for additional required
- *   configuration.
+ * specified as `"none"`. The supported types are: - `"cookie"`: On the first
+ * request to a proxied load balancer, a cookie is generated, encoding information
+ * of which origin the request will be forwarded to. Subsequent requests, by the
+ * same client to the same load balancer, will be sent to the origin server the
+ * cookie encodes, for the duration of the cookie and as long as the origin server
+ * remains healthy. If the cookie has expired or the origin server is unhealthy,
+ * then a new origin server is calculated and used. - `"ip_cookie"`: Behaves the
+ * same as `"cookie"` except the initial origin selection is stable and based on
+ * the client's ip address. - `"header"`: On the first request to a proxied load
+ * balancer, a session key based on the configured HTTP headers (see
+ * `session_affinity_attributes.headers`) is generated, encoding the request
+ * headers used for storing in the load balancer session state which origin the
+ * request will be forwarded to. Subsequent requests to the load balancer with the
+ * same headers will be sent to the same origin server, for the duration of the
+ * session and as long as the origin server remains healthy. If the session has
+ * been idle for the duration of `session_affinity_ttl` seconds or the origin
+ * server is unhealthy, then a new origin server is calculated and used. See
+ * `headers` in `session_affinity_attributes` for additional required
+ * configuration.
  */
 export type SessionAffinityParam = 'none' | 'cookie' | 'ip_cookie' | 'header';
 /**
@@ -1208,14 +1190,11 @@ export interface SessionAffinityAttributes {
     /**
      * When header `session_affinity` is enabled, this option can be used to specify
      * how HTTP headers on load balancing requests will be used. The supported values
-     * are:
-     *
-     * - `"true"`: Load balancing requests must contain _all_ of the HTTP headers
-     *   specified by the `headers` session affinity attribute, otherwise sessions
-     *   aren't created.
-     * - `"false"`: Load balancing requests must contain _at least one_ of the HTTP
-     *   headers specified by the `headers` session affinity attribute, otherwise
-     *   sessions aren't created.
+     * are: - `"true"`: Load balancing requests must contain _all_ of the HTTP headers
+     * specified by the `headers` session affinity attribute, otherwise sessions aren't
+     * created. - `"false"`: Load balancing requests must contain _at least one_ of the
+     * HTTP headers specified by the `headers` session affinity attribute, otherwise
+     * sessions aren't created.
      */
     require_all_headers?: boolean;
     /**
@@ -1234,15 +1213,13 @@ export interface SessionAffinityAttributes {
     /**
      * Configures the zero-downtime failover between origins within a pool when session
      * affinity is enabled. This feature is currently incompatible with Argo, Tiered
-     * Cache, and Bandwidth Alliance. The supported values are:
-     *
-     * - `"none"`: No failover takes place for sessions pinned to the origin (default).
-     * - `"temporary"`: Traffic will be sent to another other healthy origin until the
-     *   originally pinned origin is available; note that this can potentially result
-     *   in heavy origin flapping.
-     * - `"sticky"`: The session affinity cookie is updated and subsequent requests are
-     *   sent to the new origin. Note: Zero-downtime failover with sticky sessions is
-     *   currently not supported for session affinity by header.
+     * Cache, and Bandwidth Alliance. The supported values are: - `"none"`: No failover
+     * takes place for sessions pinned to the origin (default). - `"temporary"`:
+     * Traffic will be sent to another other healthy origin until the originally pinned
+     * origin is available; note that this can potentially result in heavy origin
+     * flapping. - `"sticky"`: The session affinity cookie is updated and subsequent
+     * requests are sent to the new origin. Note: Zero-downtime failover with sticky
+     * sessions is currently not supported for session affinity by header.
      */
     zero_downtime_failover?: 'none' | 'temporary' | 'sticky';
 }
@@ -1269,14 +1246,11 @@ export interface SessionAffinityAttributesParam {
     /**
      * When header `session_affinity` is enabled, this option can be used to specify
      * how HTTP headers on load balancing requests will be used. The supported values
-     * are:
-     *
-     * - `"true"`: Load balancing requests must contain _all_ of the HTTP headers
-     *   specified by the `headers` session affinity attribute, otherwise sessions
-     *   aren't created.
-     * - `"false"`: Load balancing requests must contain _at least one_ of the HTTP
-     *   headers specified by the `headers` session affinity attribute, otherwise
-     *   sessions aren't created.
+     * are: - `"true"`: Load balancing requests must contain _all_ of the HTTP headers
+     * specified by the `headers` session affinity attribute, otherwise sessions aren't
+     * created. - `"false"`: Load balancing requests must contain _at least one_ of the
+     * HTTP headers specified by the `headers` session affinity attribute, otherwise
+     * sessions aren't created.
      */
     require_all_headers?: boolean;
     /**
@@ -1295,15 +1269,13 @@ export interface SessionAffinityAttributesParam {
     /**
      * Configures the zero-downtime failover between origins within a pool when session
      * affinity is enabled. This feature is currently incompatible with Argo, Tiered
-     * Cache, and Bandwidth Alliance. The supported values are:
-     *
-     * - `"none"`: No failover takes place for sessions pinned to the origin (default).
-     * - `"temporary"`: Traffic will be sent to another other healthy origin until the
-     *   originally pinned origin is available; note that this can potentially result
-     *   in heavy origin flapping.
-     * - `"sticky"`: The session affinity cookie is updated and subsequent requests are
-     *   sent to the new origin. Note: Zero-downtime failover with sticky sessions is
-     *   currently not supported for session affinity by header.
+     * Cache, and Bandwidth Alliance. The supported values are: - `"none"`: No failover
+     * takes place for sessions pinned to the origin (default). - `"temporary"`:
+     * Traffic will be sent to another other healthy origin until the originally pinned
+     * origin is available; note that this can potentially result in heavy origin
+     * flapping. - `"sticky"`: The session affinity cookie is updated and subsequent
+     * requests are sent to the new origin. Note: Zero-downtime failover with sticky
+     * sessions is currently not supported for session affinity by header.
      */
     zero_downtime_failover?: 'none' | 'temporary' | 'sticky';
 }
@@ -1413,7 +1385,7 @@ export interface LoadBalancerCreateParams {
      */
     networks?: Array<string>;
     /**
-     * Body param: (Enterprise only): A mapping of Cloudflare PoP identifiers to a list
+     * Body param: Enterprise only: A mapping of Cloudflare PoP identifiers to a list
      * of pool IDs (ordered by their failover priority) for the PoP (datacenter). Any
      * PoPs not explicitly defined will fall back to using the corresponding
      * country_pool, then region_pool mapping if it exists else to default_pools.
@@ -1452,28 +1424,25 @@ export interface LoadBalancerCreateParams {
     rules?: Array<RulesParam>;
     /**
      * Body param: Specifies the type of session affinity the load balancer should use
-     * unless specified as `"none"`. The supported types are:
-     *
-     * - `"cookie"`: On the first request to a proxied load balancer, a cookie is
-     *   generated, encoding information of which origin the request will be forwarded
-     *   to. Subsequent requests, by the same client to the same load balancer, will be
-     *   sent to the origin server the cookie encodes, for the duration of the cookie
-     *   and as long as the origin server remains healthy. If the cookie has expired or
-     *   the origin server is unhealthy, then a new origin server is calculated and
-     *   used.
-     * - `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
-     *   selection is stable and based on the client's ip address.
-     * - `"header"`: On the first request to a proxied load balancer, a session key
-     *   based on the configured HTTP headers (see
-     *   `session_affinity_attributes.headers`) is generated, encoding the request
-     *   headers used for storing in the load balancer session state which origin the
-     *   request will be forwarded to. Subsequent requests to the load balancer with
-     *   the same headers will be sent to the same origin server, for the duration of
-     *   the session and as long as the origin server remains healthy. If the session
-     *   has been idle for the duration of `session_affinity_ttl` seconds or the origin
-     *   server is unhealthy, then a new origin server is calculated and used. See
-     *   `headers` in `session_affinity_attributes` for additional required
-     *   configuration.
+     * unless specified as `"none"`. The supported types are: - `"cookie"`: On the
+     * first request to a proxied load balancer, a cookie is generated, encoding
+     * information of which origin the request will be forwarded to. Subsequent
+     * requests, by the same client to the same load balancer, will be sent to the
+     * origin server the cookie encodes, for the duration of the cookie and as long as
+     * the origin server remains healthy. If the cookie has expired or the origin
+     * server is unhealthy, then a new origin server is calculated and used. -
+     * `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
+     * selection is stable and based on the client's ip address. - `"header"`: On the
+     * first request to a proxied load balancer, a session key based on the configured
+     * HTTP headers (see `session_affinity_attributes.headers`) is generated, encoding
+     * the request headers used for storing in the load balancer session state which
+     * origin the request will be forwarded to. Subsequent requests to the load
+     * balancer with the same headers will be sent to the same origin server, for the
+     * duration of the session and as long as the origin server remains healthy. If the
+     * session has been idle for the duration of `session_affinity_ttl` seconds or the
+     * origin server is unhealthy, then a new origin server is calculated and used. See
+     * `headers` in `session_affinity_attributes` for additional required
+     * configuration.
      */
     session_affinity?: SessionAffinityParam;
     /**
@@ -1484,14 +1453,12 @@ export interface LoadBalancerCreateParams {
      * Body param: Time, in seconds, until a client's session expires after being
      * created. Once the expiry time has been reached, subsequent requests may get sent
      * to a different origin server. The accepted ranges per `session_affinity` policy
-     * are:
-     *
-     * - `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used
-     *   unless explicitly set. The accepted range of values is between [1800, 604800].
-     * - `"header"`: The current default of 1800 seconds will be used unless explicitly
-     *   set. The accepted range of values is between [30, 3600]. Note: With session
-     *   affinity by header, sessions only expire after they haven't been used for the
-     *   number of seconds specified.
+     * are: - `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used
+     * unless explicitly set. The accepted range of values is between [1800, 604800]. -
+     * `"header"`: The current default of 1800 seconds will be used unless explicitly
+     * set. The accepted range of values is between [30, 3600]. Note: With session
+     * affinity by header, sessions only expire after they haven't been used for the
+     * number of seconds specified.
      */
     session_affinity_ttl?: number;
     /**
@@ -1583,7 +1550,7 @@ export interface LoadBalancerUpdateParams {
      */
     networks?: Array<string>;
     /**
-     * Body param: (Enterprise only): A mapping of Cloudflare PoP identifiers to a list
+     * Body param: Enterprise only: A mapping of Cloudflare PoP identifiers to a list
      * of pool IDs (ordered by their failover priority) for the PoP (datacenter). Any
      * PoPs not explicitly defined will fall back to using the corresponding
      * country_pool, then region_pool mapping if it exists else to default_pools.
@@ -1622,28 +1589,25 @@ export interface LoadBalancerUpdateParams {
     rules?: Array<RulesParam>;
     /**
      * Body param: Specifies the type of session affinity the load balancer should use
-     * unless specified as `"none"`. The supported types are:
-     *
-     * - `"cookie"`: On the first request to a proxied load balancer, a cookie is
-     *   generated, encoding information of which origin the request will be forwarded
-     *   to. Subsequent requests, by the same client to the same load balancer, will be
-     *   sent to the origin server the cookie encodes, for the duration of the cookie
-     *   and as long as the origin server remains healthy. If the cookie has expired or
-     *   the origin server is unhealthy, then a new origin server is calculated and
-     *   used.
-     * - `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
-     *   selection is stable and based on the client's ip address.
-     * - `"header"`: On the first request to a proxied load balancer, a session key
-     *   based on the configured HTTP headers (see
-     *   `session_affinity_attributes.headers`) is generated, encoding the request
-     *   headers used for storing in the load balancer session state which origin the
-     *   request will be forwarded to. Subsequent requests to the load balancer with
-     *   the same headers will be sent to the same origin server, for the duration of
-     *   the session and as long as the origin server remains healthy. If the session
-     *   has been idle for the duration of `session_affinity_ttl` seconds or the origin
-     *   server is unhealthy, then a new origin server is calculated and used. See
-     *   `headers` in `session_affinity_attributes` for additional required
-     *   configuration.
+     * unless specified as `"none"`. The supported types are: - `"cookie"`: On the
+     * first request to a proxied load balancer, a cookie is generated, encoding
+     * information of which origin the request will be forwarded to. Subsequent
+     * requests, by the same client to the same load balancer, will be sent to the
+     * origin server the cookie encodes, for the duration of the cookie and as long as
+     * the origin server remains healthy. If the cookie has expired or the origin
+     * server is unhealthy, then a new origin server is calculated and used. -
+     * `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
+     * selection is stable and based on the client's ip address. - `"header"`: On the
+     * first request to a proxied load balancer, a session key based on the configured
+     * HTTP headers (see `session_affinity_attributes.headers`) is generated, encoding
+     * the request headers used for storing in the load balancer session state which
+     * origin the request will be forwarded to. Subsequent requests to the load
+     * balancer with the same headers will be sent to the same origin server, for the
+     * duration of the session and as long as the origin server remains healthy. If the
+     * session has been idle for the duration of `session_affinity_ttl` seconds or the
+     * origin server is unhealthy, then a new origin server is calculated and used. See
+     * `headers` in `session_affinity_attributes` for additional required
+     * configuration.
      */
     session_affinity?: SessionAffinityParam;
     /**
@@ -1654,14 +1618,12 @@ export interface LoadBalancerUpdateParams {
      * Body param: Time, in seconds, until a client's session expires after being
      * created. Once the expiry time has been reached, subsequent requests may get sent
      * to a different origin server. The accepted ranges per `session_affinity` policy
-     * are:
-     *
-     * - `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used
-     *   unless explicitly set. The accepted range of values is between [1800, 604800].
-     * - `"header"`: The current default of 1800 seconds will be used unless explicitly
-     *   set. The accepted range of values is between [30, 3600]. Note: With session
-     *   affinity by header, sessions only expire after they haven't been used for the
-     *   number of seconds specified.
+     * are: - `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used
+     * unless explicitly set. The accepted range of values is between [1800, 604800]. -
+     * `"header"`: The current default of 1800 seconds will be used unless explicitly
+     * set. The accepted range of values is between [30, 3600]. Note: With session
+     * affinity by header, sessions only expire after they haven't been used for the
+     * number of seconds specified.
      */
     session_affinity_ttl?: number;
     /**
@@ -1755,7 +1717,7 @@ export interface LoadBalancerEditParams {
      */
     name?: string;
     /**
-     * Body param: (Enterprise only): A mapping of Cloudflare PoP identifiers to a list
+     * Body param: Enterprise only: A mapping of Cloudflare PoP identifiers to a list
      * of pool IDs (ordered by their failover priority) for the PoP (datacenter). Any
      * PoPs not explicitly defined will fall back to using the corresponding
      * country_pool, then region_pool mapping if it exists else to default_pools.
@@ -1794,28 +1756,25 @@ export interface LoadBalancerEditParams {
     rules?: Array<RulesParam>;
     /**
      * Body param: Specifies the type of session affinity the load balancer should use
-     * unless specified as `"none"`. The supported types are:
-     *
-     * - `"cookie"`: On the first request to a proxied load balancer, a cookie is
-     *   generated, encoding information of which origin the request will be forwarded
-     *   to. Subsequent requests, by the same client to the same load balancer, will be
-     *   sent to the origin server the cookie encodes, for the duration of the cookie
-     *   and as long as the origin server remains healthy. If the cookie has expired or
-     *   the origin server is unhealthy, then a new origin server is calculated and
-     *   used.
-     * - `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
-     *   selection is stable and based on the client's ip address.
-     * - `"header"`: On the first request to a proxied load balancer, a session key
-     *   based on the configured HTTP headers (see
-     *   `session_affinity_attributes.headers`) is generated, encoding the request
-     *   headers used for storing in the load balancer session state which origin the
-     *   request will be forwarded to. Subsequent requests to the load balancer with
-     *   the same headers will be sent to the same origin server, for the duration of
-     *   the session and as long as the origin server remains healthy. If the session
-     *   has been idle for the duration of `session_affinity_ttl` seconds or the origin
-     *   server is unhealthy, then a new origin server is calculated and used. See
-     *   `headers` in `session_affinity_attributes` for additional required
-     *   configuration.
+     * unless specified as `"none"`. The supported types are: - `"cookie"`: On the
+     * first request to a proxied load balancer, a cookie is generated, encoding
+     * information of which origin the request will be forwarded to. Subsequent
+     * requests, by the same client to the same load balancer, will be sent to the
+     * origin server the cookie encodes, for the duration of the cookie and as long as
+     * the origin server remains healthy. If the cookie has expired or the origin
+     * server is unhealthy, then a new origin server is calculated and used. -
+     * `"ip_cookie"`: Behaves the same as `"cookie"` except the initial origin
+     * selection is stable and based on the client's ip address. - `"header"`: On the
+     * first request to a proxied load balancer, a session key based on the configured
+     * HTTP headers (see `session_affinity_attributes.headers`) is generated, encoding
+     * the request headers used for storing in the load balancer session state which
+     * origin the request will be forwarded to. Subsequent requests to the load
+     * balancer with the same headers will be sent to the same origin server, for the
+     * duration of the session and as long as the origin server remains healthy. If the
+     * session has been idle for the duration of `session_affinity_ttl` seconds or the
+     * origin server is unhealthy, then a new origin server is calculated and used. See
+     * `headers` in `session_affinity_attributes` for additional required
+     * configuration.
      */
     session_affinity?: SessionAffinityParam;
     /**
@@ -1826,14 +1785,12 @@ export interface LoadBalancerEditParams {
      * Body param: Time, in seconds, until a client's session expires after being
      * created. Once the expiry time has been reached, subsequent requests may get sent
      * to a different origin server. The accepted ranges per `session_affinity` policy
-     * are:
-     *
-     * - `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used
-     *   unless explicitly set. The accepted range of values is between [1800, 604800].
-     * - `"header"`: The current default of 1800 seconds will be used unless explicitly
-     *   set. The accepted range of values is between [30, 3600]. Note: With session
-     *   affinity by header, sessions only expire after they haven't been used for the
-     *   number of seconds specified.
+     * are: - `"cookie"` / `"ip_cookie"`: The current default of 23 hours will be used
+     * unless explicitly set. The accepted range of values is between [1800, 604800]. -
+     * `"header"`: The current default of 1800 seconds will be used unless explicitly
+     * set. The accepted range of values is between [30, 3600]. Note: With session
+     * affinity by header, sessions only expire after they haven't been used for the
+     * number of seconds specified.
      */
     session_affinity_ttl?: number;
     /**