Add 2 random secret in the private repo for use with github to trigger silverblue and coreos automated builds.
See https://docs.okd.io/latest/dev_guide/builds/triggering_builds.html#github-webhooks and commit 185a24c325d8b1.
The 2 secrets should be in variable named silverblue_github_secret and coreos_github_secret. I will then need to have the output of "oc describe bc/silverblue-build" and "oc describe bc/coreos-build". That's not a highly critical secret (a leak would just mean someone can trigger rebuild of the container, so at worst a denial of service I guess), but that's more consistant to use that. you can just give them to me on irc, no need for gpg/etc. I will take care of the github side integration.
When do you need this? (YYYY/MM/DD) When you have time
When is this no longer needed or useful? (YYYY/MM/DD) Wehn we will decide to rename coreos and silverblue, aka in 3 years given past rename :p
If we cannot complete your request, what is the impact? I would be very sad, and likely not bring candies in Flock next time
So, later, I would also need a 3rd secret: containers_github_secret for containers.fedoraproject.org, once I push that one, see https://pagure.io/fedora-infrastructure/issue/7120
Done.
I have also made stg versions: silverblue_stg_github_secret, coreos_stg_github_secret, containers_stg_github_secret.
The buildconfig info is in ~misc/buildinfo on batcave01 for each of the apps (staging then prod).
Please let us know if you need anything further.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.