#9680 Adding sigkey requirement to the odcs private compose generation
Merged 10 months ago by mohanboddu. Opened 10 months ago by mohanboddu.
mohanboddu/releng private-odcs-all-arches  into  master

@@ -9,7 +9,7 @@ 




- Usage: python odcs-private-compose.py <token> <koji_tag>

+ Usage: python odcs-private-compose.py <token> <koji_tag> <sigkey>


  This is used to generate private composes using ODCS.

  This script is specifically used to generate openh264 repos.
@@ -25,15 +25,17 @@ 

  parser = argparse.ArgumentParser()

  parser.add_argument("token", help="OIDC token for authenticating to ODCS")

  parser.add_argument("tag", help="koji tag to compose")

+ parser.add_argument("sigkey", help="sigkey that was used to signed the builds in the tag")

  args = parser.parse_args()

  token = args.token

  tag = args.tag

+ sigkey = args.sigkey


  odcs = ODCS("https://odcs.fedoraproject.org",




- source = ComposeSourceTag(tag)

+ source = ComposeSourceTag(tag, sigkeys=[sigkey])


  # Making a private compose with no inheritance

  arches = ["armv7hl", "i686", "x86_64", "aarch64", "ppc64le", "s390x"]

rebased onto 5703b131307341ef3763b31c904984bd18d5b8ab

10 months ago

Sigkeys are passed to ComposeSourceTag like this (if you want just single signing key to be used):

source = ComposeSourceTag(tag, sigkeys=[sigkey])

rebased onto 496deb1a33e8038aa6f25c64fcac7e5f099d717d

10 months ago

rebased onto 850d443

10 months ago

+1, I think this should work. You can always check resulting compose in the ODCS API by its ID and see what "sigkeys" value is there.

Pull-Request has been merged by mohanboddu

10 months ago