This repository contains GitHub Actions for Elastic Observability projects.
The repository is organized by action namespace. Each action directory contains its own action.yml and usage README.
The repository uses multiple .github/workflows/trigger-oblt-aw-*.yml workflows to forward scoped repository events to reusable workflows in elastic/oblt-aw.
Current trigger workflows include:
.github/workflows/trigger-oblt-aw-issue-comment.yml.github/workflows/trigger-oblt-aw-issues.yml.github/workflows/trigger-oblt-aw-pull-request.yml.github/workflows/trigger-oblt-aw-schedule.yml.github/workflows/trigger-oblt-aw-status.yml
Secret forwarding currently works as follows:
- These trigger workflows do not explicitly forward
COPILOT_GITHUB_TOKEN. .github/workflows/trigger-oblt-aw-status.ymlmapsBUILDKITE_LOGS_API_TOKENtoBUILDKITE_API_TOKEN.
Keep this inventory and the secret mappings synchronized when trigger workflows are added or removed.
The oblt-cli/deploy-my-kibana and oblt-cli/undeploy-my-kibana actions create issues in elastic/observability-test-environments:
deploy-my-kibanacreates an issue labeleddeploy-custom-kibanaundeploy-my-kibanacreates an issue labeleddestroy-custom-kibana-serverless
When using these actions, provide credentials with issues: write permission on elastic/observability-test-environments.
The repository includes the .github/workflows/updatecli.yml workflow, which runs Updatecli compose automation against oblt-actions and oblt-cli.
It runs on:
- a weekly schedule (
0 6 * * 6) - manual dispatch (
workflow_dispatch)
This workflow requires the repository secrets OBS_AUTOMATION_APP_ID and OBS_AUTOMATION_APP_PEM to generate a GitHub App token with write access to contents and pull requests for the target repositories. It also requires SLACK_BOT_TOKEN so the job can notify #observablt-bots when the updatecli run fails.
The repository-local workflow inventory and per-workflow documentation are
indexed in .github/workflows/README.md.
See RELEASE.md for the release process.
Made with