You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/test-framework-dev-guide.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,17 @@ The Elastic Agent package that is used for integration tests packages Beats buil
28
28
ESS (production) API Key to create on <https://cloud.elastic.co/account/keys>
29
29
Warning: if you never created a deployment on it, you won't have permission to get this key, so you will need to create one first.
30
30
31
+
32
+
#### Setup Serverless deployment
33
+
34
+
This process is now automated and runs daily, utilizing the existing `oblt-cli` framework. Serverless deployments are created each day and automatically destroyed every three days.
35
+
36
+
The automation is configured in the `serverless-project.yml` file located in the `.github/workflows` directory.
37
+
38
+
If necessary, you can create a new serverless deployment manually; the previous deployments will be destroyed automatically, but not immediately. To do so, you need to run the GitHub action called [serverless-project.yml](https://github.com/elastic/elastic-agent/actions/workflows/serverless-project.yml).
39
+
40
+
Credentials for these deployments are securely stored in Google and can only be accessed by Buildkite pipelines. The access control is set using [OpenID Connect in Google Cloud Platform](https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform). And that's managed by the Robots team.
41
+
31
42
## Running tests
32
43
33
44
Some integration and E2E tests are safe to run locally. These tests set
0 commit comments