consider using krew-release-bot for publishing plugin releases

[rajatjindal]

What would you like to be added

I have created krew-release-bot to auto publish new plugin releases to krew-index repo.

Why is this needed

it automates the publishing step to krew-index repo and therefore reduce the manual step needed.

If its ok with who-can authors, I can open a PR to start using that for auto publishing the releases or you can look at the travis example here, and configure it.

Many thanks for considering.
Rajat Jindal

[danielpacak]

What would you like to be added

I have created krew-release-bot to auto publish new plugin releases to krew-index repo.

Why is this needed

it automates the publishing step to krew-index repo and therefore reduce the manual step needed.

If its ok with who-can authors, I can open a PR to start using that for auto publishing the releases or you can look at the travis example here, and configure it.

Many thanks for considering.
Rajat Jindal

Hi @rajatjindal and thank your for opening the issue. I love the idea and always opt in for any possible automation. I'm just wondering wether we should migrate from Travis to GitHub Actions first and then add your bot or give it a try with Travis. @lizrice WDYT?

[rajatjindal]

Thanks for taking out time to reply, If its ok with you, i can open PR with migration to github actions + the bot I see that you are using goreleaser, so it should be relatively straight forward.

[danielpacak]

Thanks for taking out time to reply, If its ok with you, i can open PR with migration to github actions + the bot I see that you are using goreleaser, so it should be relatively straight forward.

Sorry for not replying sooner to that @rajatjindal

Before we proceed I'd like to understand the runtime / sandbox environment of the bot. Does that mean that the bot has access to encrypted secrets configured for the GitHub project? If such access is not granted by default, does that mean that we could only pass secrets and other sensitive data as environment variables or command args?

[rajatjindal]

Np.

The bot itself do not require any secrets and in github actions by default it does not have access to secrets (thats my understanding, pls correct me if thats not right)

All we need is access to releases (to calculate sha256) and krew template file.

Hope that helps

[danielpacak]

Np.

The bot itself do not require any secrets and in github actions by default it does not have access to secrets (thats my understanding, pls correct me if thats not right)

All we need is access to releases (to calculate sha256) and krew template file.

Hope that helps

I checked on my end and indeed the bot does not require access to project secrets: https://krew.sigs.k8s.io/docs/developer-guide/release/updating-plugins/

With that I'd love to automate it. What do you think about splitting the work into two tasks:

• Migrate to GitHub Actions
• Add krew-release-bot to the workflow config

/cc @lizrice

[krol3]

I'd to help :), I will start to work it