feat: add interactive automation

[bwplotka]

FYI: I finalized and stabilized all scripts in #1817

This is a PR for a feature branch to adds more interactive scripts for common OSS release (or pre-release) operations.

See gmp:toil-automation

This has to be reviewed and cleaned, but I already use it on our repos and I recommend trying it out and contributing to this branch! (e.g. PR on top of the scripts branch).

I will write playbooks/readme, but keeping it here for now:

How to use / What works now

• Clone this repo on this branch. It's easier if you have a separate repo clone for script code

git clone --single-branch -b scripts https://github.com/GoogleCloudPlatform/prometheus-engine.git pescripts

• Go to this repo root, you can execute all commands from this place.

cd pescripts

• All scripts should work on all our repos (prometheus, alertmanager, prometheus-engine).
• All scripts should be readable. Just check what they do if you have questions.
• They all follow same similar "checkout flow":
  • CHECKOUT_DIR is where you expect prometheus, alertmanager, prometheus-engine clones. If you use a dir with existing clones (recommended as cloning is slow!), script will ask you if you want to reuse it y, hard reset it n or cancel (ctrl+c). I typically say y for quick workflows and my repos are in ~/Repos.
  • PR_BRANCH typically "working" branch and something that script will force push (if you allow, it will ask).
  • BRANCH origin branch, it matters to understand what repo you refer to (AM, Prom or prometheus-engine) and for cases when repo in CHECKOUT_DIR has to be recreated.

Vulnerability check + upgrade

./hack/release-vulnfix.sh script ensures our artifacts has no artifacts (except NPM):

bash ./hack/release-vulnfix.sh help

For example to iterate quickly on ~/Repos/prometheus-engine repo, with bump-img14 branched manually checked in, I can run:

BRANCH=release/0.14 PR_BRANCH=bump-img14 CHECKOUT_DIR=~/Repos bash ./hack/release-vulnfix.sh

Long term plan

• get this reviewed and cleaned
• update playbook (as a secondary "tab" to manual process explanation)
• move to git worktree (thx @bernot-dev for suggesting).
• build TUI for it reusing https://github.com/jesseduffield/lazygit architecture and Go code for UI parts. (: All in OSS ideally.

[bernot-dev]

Your instructions for cloning the branch looks like what git worktree does, except you don't have to clone again with a worktree.

[bwplotka]

Discussion with @bernot-dev: Should this be on CI.

[bwplotka]

Replaced by #1817