|
|
@@ -3473,8 +3473,11 @@ a period of time. Feel free to reopen if you want to get back on it.</p>
|
|
|
<h3 id="triggering-e2e-tests">Triggering e2e tests</h3>
|
|
|
<p>We have an extensive set of e2e tests that test the integration with <em>real</em> cloud provider APIs.
|
|
|
Maintainers must trigger these kind of tests manually for PRs that come from forked repositories. These tests run inside a <code>kind</code> cluster in the GitHub Actions runner:</p>
|
|
|
-<div class="highlight"><pre><span></span><code>/ok-to-test sha=xxxxxx
|
|
|
+<p><div class="highlight"><pre><span></span><code>/ok-to-test sha=<full_commit_hash>
|
|
|
</code></pre></div>
|
|
|
+Examples:
|
|
|
+<div class="highlight"><pre><span></span><code>/ok-to-test sha=b8ca0040200a7a05d57048d86a972fdf833b8c9b
|
|
|
+</code></pre></div></p>
|
|
|
<h4 id="executing-e2e-tests-locally">Executing e2e tests locally</h4>
|
|
|
<p>You have to prepare your shell environment with the necessary variables so the e2e test
|
|
|
runner knows what credentials to use. See <code>e2e/run.sh</code> for the variables that are passed in.
|
gusfcarvalho