elastic / elastic/cloudbeat

[GA Workflow] Revisit sync cloudbeat version to hermit workflow

Open
#3,267 0 comments 0 reactions 0 assignees View on GitHub
cloudbeat Team:Cloud Security
Dominant language
Go
Stars
58
Forks
55
Avg merge
9h 9m
Merged PRs (30d)
424

Description

Hermit variables file `bin/hermit.hcl` uses the CLOUDBEAT_VERSION as part of ELK_VERSION, which is used on our CIs.

It indicates the Docker images / elastic stack version that will be used.

If we bump if just after the bump of `version.go`, the elk/docker image will not be available, at least for a while, and the first CI runs will fail.

We should explore other approaches on that sync like:
* Run it manually days after the bump (and update the workflow to open PR)
* Run it automatically some days after the bump if possible (and update the workflow to open PR)

Note: Apart from that this workflow needs a minor fix, to add hermit init as a step before running the script

```diff
--- a/.github/workflows/sync-internal-cloudbeat-version.yml
+++ b/.github/workflows/sync-internal-cloudbeat-version.yml
@@ -14,6 +14,9 @@ jobs:
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
with:
ref: ${{ github.ref }}
+ - name: Initialize hermit
+ shell: bash
+ run: ./bin/hermit env --raw >> "$GITHUB_ENV"
- name: Synchronize versions using a script
run: |
./scripts/sync_internal_cloudbeat_version.sh
```

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.