github-actions(updatecli): use GitHub secrets without vault access

v1v commented 1 month ago

Summary of your changes

email is not required.
Use CLOUDSEC_MACHINE_TOKEN to create PRs when running updatecli.
Use the GitHub actions rather than the apm-pipeline-library
Avoid using VAULT_ secrets

Once this is merged can the below secrets being deleted?

VAULT_ROLE_ID
VAULT_SECRET_ID

They were created in https://github.com/elastic/cloudbeat/pull/749 but won't be needed.

Screenshot/Data

Related Issues

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[bot] commented 1 month ago

This pull request does not have a backport label. Could you fix it @v1v? 🙏 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[bot] commented 1 month ago

:bar_chart: Allure Report - :green_heart: No failures were reported.

Result	Count
🟥 Failed	0
🟩 Passed	359
⬜ Skipped	33

elastic / cloudbeat