attempt to fix ga hermit cache

[moukoublen]

Summary of your changes

Screenshot/Data

Related Issues

Fixes: #1175

Checklist

• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary README/documentation (if appropriate)

Introducing a new rule?

• Generate rule metadata using this script
• Add relevant unit tests
• Generate relevant rule templates using this script, and open a PR in elastic/packages/cloud_security_posture

[mergify]

This pull request does not have a backport label. Could you fix it @moukoublen? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[github-actions]

📊 Allure Report - 💚 No failures were reported.

Result	Count
🟥 Failed	0
🟩 Passed	39
⬜ Skipped	1

[orestisfl]

What about https://github.com/cashapp/activate-hermit that has a cache option?

[moukoublen]

@orestisfl that was my first thought but we need some extra directories in cache that are not included in https://github.com/cashapp/activate-hermit.

We need (so far):

          ~/.cache/hermit/pkg
          ./.hermit
          ~/.cache/go-build
          ~/go/pkg/
          ~/.cache/pre-commit

This is still draft. I am stiil thinking about the optimal way to separate the caches in order not to get overwritten (because cloudbeat has a lot workflows that run in parallel using the same -or not- cache).

[orestisfl]

Great, thanks. How are we going to handle the case where different items are cached depending on the pipeline? For example, opa pipelines will just initialize opa while go tests will initialize ~/go as well.

[moukoublen]

This is what I meant when I wrote that I am still thinking about the optimal way to separate the caches in order not to get overwritten. Different pipelines run in parallel and might initialize different parts of "cache". (Hermit install at the beginning is the easy part and already implemented. The difficult part are python envs, go pks and pre-commit cache).

This is still wip

[moukoublen]

closed due to this: #2000