Login to docker to fix workflow #526

Merged
pat-s merged 4 commits from refs/pull/526/head into main 2023-10-10 19:48:00 +00:00
pat-s commented 2023-10-05 19:53:02 +00:00 (Migrated from gitea.com)

Same as for the release workflow.

Same as for the release workflow.
techknowlogick (Migrated from gitea.com) reviewed 2023-10-06 04:07:37 +00:00
techknowlogick (Migrated from gitea.com) left a comment

blocking this as it opens up secrets to PRs

blocking this as it opens up secrets to PRs
pat-s commented 2023-10-06 07:05:06 +00:00 (Migrated from gitea.com)

Good catch.

I see two solutions:

  • a read-only token
  • selectively approving PRs

I'd favor (1). Your opinion?

Good catch. I see two solutions: - a read-only token - selectively approving PRs I'd favor (1). Your opinion?
pat-s commented 2023-10-09 18:37:41 +00:00 (Migrated from gitea.com)

@techknowlogick I've used a personal read-only public token of my own Docker account now to move forward. If you have time, it would be great to add a token from the Gitea docker org. Public read-only tokens should only have a use case for rate limiting AFAICS.

@techknowlogick I've used a personal read-only public token of my own Docker account now to move forward. If you have time, it would be great to add a token from the Gitea docker org. Public read-only tokens should only have a use case for rate limiting AFAICS.
techknowlogick commented 2023-10-09 23:32:04 +00:00 (Migrated from gitea.com)

@pat-s I've created some temporary RO tokens DOCKER_RO_USERNAME and DOCKER_RO_PASSWORD under my personal username, as I'm having some trouble getting into the giteabot docker hub account. Once I get access, I'll be able to update them :)

@pat-s I've created some temporary RO tokens `DOCKER_RO_USERNAME` and `DOCKER_RO_PASSWORD` under my personal username, as I'm having some trouble getting into the giteabot docker hub account. Once I get access, I'll be able to update them :)
pat-s commented 2023-10-10 07:05:48 +00:00 (Migrated from gitea.com)

Thanks! Though this wouldn't have been needed as my last comment tried to communicate I already did the same with DOCKER_USERNAME_PUBLIC 😄

For now, I only need an approval here to move forward. I want to get the renovate updates auto-merged again.

Thanks! Though this wouldn't have been needed as my last comment tried to communicate I already did the same with `DOCKER_USERNAME_PUBLIC` 😄 For now, I only need an approval here to move forward. I want to get the renovate updates auto-merged again.
Sign in to join this conversation.
No description provided.