Push-based publish job is failing

Question

detiber opened this issue 4 years ago · 7 comments

Expected Behaviour

Current publish job is referencing a non-existing s3 bucket and does not have credentials, example failure: https://github.com/tinkerbell/hook/actions/runs/559080308

Answer 1 · 2021-02-12T08:20:00.000Z

@rawkode is on it asking CNCF for an AWS|GCP access to get an s3 bucket up and running for us.

Answer 2 · 2021-02-12T09:39:05.000Z

the cncf/cluster repo is for requesting EM resources only, so I'm currently finding out the best course of action. I'll update later today.

Answer 3 · 2021-03-18T14:51:44.000Z

Answer 4 · 2021-08-27T04:21:52.000Z

was this fixed?

Answer 5 · 2021-08-27T06:39:46.000Z

was this fixed?

We have access to a S3 bucket, details are on 1Password

Answer 6 · 2021-10-19T15:10:28.000Z

Since we are using GitHub releases now, is this still needed?

Answer 7 · 2021-10-19T15:17:56.000Z

I guess not, we can easily had a few lines together that parse the GitHub API and get a release URL to download.