For the https://pagure.io/workstation-ostree-config project, I would like to create Zuul jobs that update the content of the repo and open a Pull Request with the update
To avoid using a personal token, we would need a dedicated account in pagure / a role in Zuul (?) with an API key with pull request access to (all?) repos.
This is similar in concept to how jobs running as GitHub Actions are given a GitHub Token that has a limited access to the GitHub API.
Notes: - We can use the API to open PRs: https://pagure.io/api/0/#pull_requests-tab
@siosm your plan sounds reasonable:
@fbo @tdecacqu hi guys, or is there some better way for this workflow in Zuul?
Metadata Update from @mvadkert: - Issue tagged with: Zuul CI
Hi @siosm and @mvadkert,
Yes that's the right way to handle this.
To create the Zuul secret for the API key, here is the process:
We could then create a Job that will use that secret and we can tell Zuul to run that job in a Periodic pipeline https://pagure.io/fedora-project-config/blob/master/f/zuul.d/_pipelines.yaml#_313