chore: update docs/dyn , add static discovery files to discovery_cache/documents (#1111)
This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/78f53313-0c78-4a29-8841-f031665a4c6a/targets
- [ ] To automatically regenerate this PR, check this box.
Source-Link: https://github.com/googleapis/synthtool/commit/c2de32114ec484aa708d32012d1fa8d75232daf5
diff --git a/docs/dyn/pubsublite_v1.admin.projects.locations.topics.html b/docs/dyn/pubsublite_v1.admin.projects.locations.topics.html
index c3ce30b..2389c29 100644
--- a/docs/dyn/pubsublite_v1.admin.projects.locations.topics.html
+++ b/docs/dyn/pubsublite_v1.admin.projects.locations.topics.html
@@ -124,12 +124,12 @@
"period": "A String", # How long a published message is retained. If unset, messages will be retained as long as the bytes retained for each partition is below `per_partition_bytes`.
},
"partitionConfig": { # The settings for a topic's partitions. # The settings for this topic's partitions.
- "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
- "count": "A String", # The number of partitions in the topic. Must be at least 1.
"capacity": { # The throughput capacity configuration for each partition. # The capacity configuration.
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
},
+ "count": "A String", # The number of partitions in the topic. Must be at least 1.
+ "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
},
"name": "A String", # The name of the topic. Structured like: projects/{project_number}/locations/{location}/topics/{topic_id}
}
@@ -149,12 +149,12 @@
"period": "A String", # How long a published message is retained. If unset, messages will be retained as long as the bytes retained for each partition is below `per_partition_bytes`.
},
"partitionConfig": { # The settings for a topic's partitions. # The settings for this topic's partitions.
- "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
- "count": "A String", # The number of partitions in the topic. Must be at least 1.
"capacity": { # The throughput capacity configuration for each partition. # The capacity configuration.
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
},
+ "count": "A String", # The number of partitions in the topic. Must be at least 1.
+ "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
},
"name": "A String", # The name of the topic. Structured like: projects/{project_number}/locations/{location}/topics/{topic_id}
}</pre>
@@ -198,12 +198,12 @@
"period": "A String", # How long a published message is retained. If unset, messages will be retained as long as the bytes retained for each partition is below `per_partition_bytes`.
},
"partitionConfig": { # The settings for a topic's partitions. # The settings for this topic's partitions.
- "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
- "count": "A String", # The number of partitions in the topic. Must be at least 1.
"capacity": { # The throughput capacity configuration for each partition. # The capacity configuration.
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
},
+ "count": "A String", # The number of partitions in the topic. Must be at least 1.
+ "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
},
"name": "A String", # The name of the topic. Structured like: projects/{project_number}/locations/{location}/topics/{topic_id}
}</pre>
@@ -252,12 +252,12 @@
"period": "A String", # How long a published message is retained. If unset, messages will be retained as long as the bytes retained for each partition is below `per_partition_bytes`.
},
"partitionConfig": { # The settings for a topic's partitions. # The settings for this topic's partitions.
- "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
- "count": "A String", # The number of partitions in the topic. Must be at least 1.
"capacity": { # The throughput capacity configuration for each partition. # The capacity configuration.
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
},
+ "count": "A String", # The number of partitions in the topic. Must be at least 1.
+ "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
},
"name": "A String", # The name of the topic. Structured like: projects/{project_number}/locations/{location}/topics/{topic_id}
},
@@ -295,12 +295,12 @@
"period": "A String", # How long a published message is retained. If unset, messages will be retained as long as the bytes retained for each partition is below `per_partition_bytes`.
},
"partitionConfig": { # The settings for a topic's partitions. # The settings for this topic's partitions.
- "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
- "count": "A String", # The number of partitions in the topic. Must be at least 1.
"capacity": { # The throughput capacity configuration for each partition. # The capacity configuration.
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
},
+ "count": "A String", # The number of partitions in the topic. Must be at least 1.
+ "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
},
"name": "A String", # The name of the topic. Structured like: projects/{project_number}/locations/{location}/topics/{topic_id}
}
@@ -320,12 +320,12 @@
"period": "A String", # How long a published message is retained. If unset, messages will be retained as long as the bytes retained for each partition is below `per_partition_bytes`.
},
"partitionConfig": { # The settings for a topic's partitions. # The settings for this topic's partitions.
- "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
- "count": "A String", # The number of partitions in the topic. Must be at least 1.
"capacity": { # The throughput capacity configuration for each partition. # The capacity configuration.
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
},
+ "count": "A String", # The number of partitions in the topic. Must be at least 1.
+ "scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
},
"name": "A String", # The name of the topic. Structured like: projects/{project_number}/locations/{location}/topics/{topic_id}
}</pre>