autoperibolossync
autoperibolossync
is a like wrapper over the private-org-peribolos-sync tool.
What it does
autoperibolossync
maintains the Peribolos configuration stored in a GitHub repository by executing
the private-org-peribolos-sync over a working copy of a repository containing Peribolos
config and filing a PR to that repository if the underlying tool changes the config.
Why it exists
Together with private-org-peribolos-sync it
manages Peribolos configuration of the
GitHub repositories in
the openshift-priv organization.
At the time when private-org-peribolos-sync was written, there was no shared bump PR
package available, so we tended to write config-changing-tool | auto-config-changing-tool
pairs when we needed to
maintain certain configuration automatically in GitHub repositories rather than include the PR filing logic in each
configuration changing binary.
How it works
autoperibolossync
runs private-org-peribolos-sync over a working copy of a repository
containing Peribolos config. If the execution results in Peribolos changes, the tool submits or updates a pull request
in that repository that updates the mainline with the changes, using
Prow's generic-autobumper package.
How is it deployed
The periodic
job periodic-auto-private-org-peribolos-sync (definition)
uses autoperibolossync
to
create PRs in openshift/config (
the repository is private).