Deploying to gh-pages from @ e35702e 🚀

googleforgames · Oct 10, 2023 · 61e544e · 61e544e
1 parent 1e1e289
commit 61e544e
Show file tree

Hide file tree

Showing 8 changed files with 25 additions and 9 deletions.
diff --git a/...runner/work/quilkin/quilkin/target/debug/build/quilkin-805b3829c829f320/out/built.rs.html b/...runner/work/quilkin/quilkin/target/debug/build/quilkin-805b3829c829f320/out/built.rs.html
@@ -217,7 +217,7 @@
 </span><span class="kw">pub const </span>CFG_POINTER_WIDTH: <span class="kw-2">&amp;</span>str = <span class="string">r&quot;64&quot;</span>;
 <span class="attr">#[doc=<span class="string">r#&quot;If the crate was compiled from within a git-repository, `GIT_VERSION` contains HEAD&#39;s tag. The short commit id is used if HEAD is not tagged.&quot;#</span>]
 #[allow(dead_code)]
-</span><span class="kw">pub const </span>GIT_VERSION: <span class="prelude-ty">Option</span>&lt;<span class="kw-2">&amp;</span>str&gt; = <span class="prelude-val">Some</span>(<span class="string">&quot;98af104&quot;</span>);
+</span><span class="kw">pub const </span>GIT_VERSION: <span class="prelude-ty">Option</span>&lt;<span class="kw-2">&amp;</span>str&gt; = <span class="prelude-val">Some</span>(<span class="string">&quot;e35702e&quot;</span>);
 <span class="attr">#[doc=<span class="string">r#&quot;If the repository had dirty/staged files.&quot;#</span>]
 #[allow(dead_code)]
 </span><span class="kw">pub const </span>GIT_DIRTY: <span class="prelude-ty">Option</span>&lt;bool&gt; = <span class="prelude-val">Some</span>(<span class="bool-val">false</span>);
@@ -227,10 +227,10 @@
 </span><span class="kw">pub const </span>GIT_HEAD_REF: <span class="prelude-ty">Option</span>&lt;<span class="kw-2">&amp;</span>str&gt; = <span class="prelude-val">Some</span>(<span class="string">&quot;refs/heads/main&quot;</span>);
 <span class="attr">#[doc=<span class="string">r#&quot;If the crate was compiled from within a git-repository, `GIT_COMMIT_HASH` contains HEAD&#39;s full commit SHA-1 hash.&quot;#</span>]
 #[allow(dead_code)]
-</span><span class="kw">pub const </span>GIT_COMMIT_HASH: <span class="prelude-ty">Option</span>&lt;<span class="kw-2">&amp;</span>str&gt; = <span class="prelude-val">Some</span>(<span class="string">&quot;98af104bbdab544ab1d514267480b950bfdb8805&quot;</span>);
+</span><span class="kw">pub const </span>GIT_COMMIT_HASH: <span class="prelude-ty">Option</span>&lt;<span class="kw-2">&amp;</span>str&gt; = <span class="prelude-val">Some</span>(<span class="string">&quot;e35702ebaa06348bf5a649b08916981f968fed75&quot;</span>);
 <span class="attr">#[doc=<span class="string">r#&quot;If the crate was compiled from within a git-repository, `GIT_COMMIT_HASH_SHORT` contains HEAD&#39;s short commit SHA-1 hash.&quot;#</span>]
 #[allow(dead_code)]
-</span><span class="kw">pub const </span>GIT_COMMIT_HASH_SHORT: <span class="prelude-ty">Option</span>&lt;<span class="kw-2">&amp;</span>str&gt; = <span class="prelude-val">Some</span>(<span class="string">&quot;98af104&quot;</span>);
+</span><span class="kw">pub const </span>GIT_COMMIT_HASH_SHORT: <span class="prelude-ty">Option</span>&lt;<span class="kw-2">&amp;</span>str&gt; = <span class="prelude-val">Some</span>(<span class="string">&quot;e35702e&quot;</span>);
 <span class="comment">//
 // EVERYTHING ABOVE THIS POINT WAS AUTO-GENERATED DURING COMPILATION. DO NOT MODIFY.
 //

diff --git a/main/book/installation.html b/main/book/installation.html
@@ -181,7 +181,7 @@ <h3 id="oci-image"><a class="header" href="#oci-image"><a href="https://us-docke
 <dl>
   <dt><strong>Source / Method</strong></dt>
   <dd>
-<pre><code>us-docker.pkg.dev/quilkin/release/quilkin:0.7.0-dev-98af104
+<pre><code>us-docker.pkg.dev/quilkin/release/quilkin:0.7.0-dev-e35702e
 </code></pre>
 </dd>
   <dt><strong>Notes</strong></dt>

diff --git a/main/book/print.html b/main/book/print.html
@@ -249,7 +249,7 @@ <h3 id="oci-image"><a class="header" href="#oci-image"><a href="https://us-docke
 <dl>
   <dt><strong>Source / Method</strong></dt>
   <dd>
-<pre><code>us-docker.pkg.dev/quilkin/release/quilkin:0.7.0-dev-98af104
+<pre><code>us-docker.pkg.dev/quilkin/release/quilkin:0.7.0-dev-e35702e
 </code></pre>
 </dd>
   <dt><strong>Notes</strong></dt>
@@ -2593,7 +2593,7 @@ <h2 id="filter-metrics"><a class="header" href="#filter-metrics">Filter Metrics<
 <tr><td>xDS</td><td>7800</td><td>gRPC (IPv4 OR IPv6)</td></tr>
 </tbody></table>
 </div>
-<p>For multi-cluster integration, Quilkin provides a <code>manage</code> service, that can be
+<p>For single-cluster integration, Quilkin provides a <code>manage</code> service, that can be
 used with a number of configuration discovery providers to provide cluster
 configuration multiple <a href="services/./proxy.html"><code>proxy</code>s</a>. With each provider automating the
 complexity of a full xDS management control plane via integrations with popular
@@ -2863,6 +2863,10 @@ <h2 id="usage"><a class="header" href="#usage">Usage</a></h2>
   -h, --help
           Print help
 </code></pre>
+<blockquote>
+<p>Each sub-control planes (<code>file</code>, <code>agones</code>, etc) matches the <code>quilkin manage</code> providers capabilities.
+Have a look at each of the <a href="services/../services/xds.html">Control Plane &gt; Providers</a> documentation for integration details.</p>
+</blockquote>
 <h2 id="quickstart"><a class="header" href="#quickstart">Quickstart</a></h2>
 <p>To get started with the relay service we need to start the relay service, and
 then setup our configuration source. For this we're going to the built-in
@@ -2955,6 +2959,10 @@ <h2 id="quickstart"><a class="header" href="#quickstart">Quickstart</a></h2>
       --sub-zone &lt;SUB_ZONE&gt;    The `sub_zone` in the `zone` in the `region` to set in the cluster map for any provider endpoints discovered [env: QUILKIN_SUB_ZONE=]
   -h, --help                   Print help
 </code></pre>
+<blockquote>
+<p>Each sub-control planes (<code>file</code>, <code>agones</code>, etc) matches the <code>quilkin manage</code> providers capabilities.
+Have a look at each of the <a href="services/../services/xds.html">Control Plane &gt; Providers</a> documentation for integration details.</p>
+</blockquote>
 <h2 id="quickstart-1"><a class="header" href="#quickstart-1">Quickstart</a></h2>
 <p>The simplest version of the <code>agent</code> service is just running <code>quilkin agent</code>,
 this will setup just the QCMP service allowing the agent to be pinged for

diff --git a/main/book/searchindex.js b/main/book/searchindex.js
diff --git a/main/book/searchindex.json b/main/book/searchindex.json
diff --git a/main/book/services/agent.html b/main/book/services/agent.html
@@ -205,6 +205,10 @@ <h1 id="control-plane-agents"><a class="header" href="#control-plane-agents">Con
       --sub-zone &lt;SUB_ZONE&gt;    The `sub_zone` in the `zone` in the `region` to set in the cluster map for any provider endpoints discovered [env: QUILKIN_SUB_ZONE=]
   -h, --help                   Print help
 </code></pre>
+<blockquote>
+<p>Each sub-control planes (<code>file</code>, <code>agones</code>, etc) matches the <code>quilkin manage</code> providers capabilities.
+Have a look at each of the <a href="../services/xds.html">Control Plane &gt; Providers</a> documentation for integration details.</p>
+</blockquote>
 <h2 id="quickstart"><a class="header" href="#quickstart">Quickstart</a></h2>
 <p>The simplest version of the <code>agent</code> service is just running <code>quilkin agent</code>,
 this will setup just the QCMP service allowing the agent to be pinged for

diff --git a/main/book/services/relay.html b/main/book/services/relay.html
@@ -211,6 +211,10 @@ <h1 id="control-plane-relay"><a class="header" href="#control-plane-relay">Contr
   -h, --help
           Print help
 </code></pre>
+<blockquote>
+<p>Each sub-control planes (<code>file</code>, <code>agones</code>, etc) matches the <code>quilkin manage</code> providers capabilities.
+Have a look at each of the <a href="../services/xds.html">Control Plane &gt; Providers</a> documentation for integration details.</p>
+</blockquote>
 <h2 id="quickstart"><a class="header" href="#quickstart">Quickstart</a></h2>
 <p>To get started with the relay service we need to start the relay service, and
 then setup our configuration source. For this we're going to the built-in

diff --git a/main/book/services/xds.html b/main/book/services/xds.html
@@ -176,7 +176,7 @@ <h1 id="xds-control-plane"><a class="header" href="#xds-control-plane">xDS Contr
 <tr><td>xDS</td><td>7800</td><td>gRPC (IPv4 OR IPv6)</td></tr>
 </tbody></table>
 </div>
-<p>For multi-cluster integration, Quilkin provides a <code>manage</code> service, that can be
+<p>For single-cluster integration, Quilkin provides a <code>manage</code> service, that can be
 used with a number of configuration discovery providers to provide cluster
 configuration multiple <a href="./proxy.html"><code>proxy</code>s</a>. With each provider automating the
 complexity of a full xDS management control plane via integrations with popular