update tag2distrepo README

This commit is contained in:
Trevor Batley 2024-11-15 10:30:11 +11:00
parent d2cc008091
commit 46fa2ea5c3

View File

@ -5,8 +5,10 @@ Koozali version which allows additional dist-repo settings
It uses the following options on a tag to control behaviour:
- `tag2distrepo_sme.enabled`: set to "true" to enable automatic distrepos
- `tag2distrepo_sme.keys`: set to a space-separated list of keys to use for distrepos
- `tag2distrepo.enabled`: set to "true" to enable automatic distrepos
- `tag2distrepo.keys`: set to a space-separated list of keys to use for distrepos
- `tag2distrepo.skip_missing_signatures`: set to "true" to skip unsigned packages (and not die)
- `tag2distrepo.allow_missing_signatures`: set to "true" to include packages with missing signatures
The tag must have at least one arch configured on it.
@ -32,7 +34,7 @@ Here is an example of enabling the plugin on an "f33-infra" tag. Create the tag
Set the extra options on the tag so the plugin will generate the repository:
koji edit-tag -x tag2distrepo_sme.enabled=True -x tag2distrepo_sme.keys=44922a28 -x tag2distrepo_sme=skip_missing_signatures=True smeserver11
koji edit-tag -x tag2distrepo.enabled=True -x tag2distrepo.keys=44922a28 -x tag2distrepo=skip_missing_signatures=True smeserver11
Tag a new build to trigger the plugin:
@ -42,12 +44,13 @@ The hub will immediately queue a new distRepo task, using the tagBuild task host
To confirm that the tag has the correct options set, use the `koji taginfo` command:
koji taginfo smeserver11
Tag: f33-infra [18680]
$ koji taginfo smeserver11
Tag: smeserver11 [39]
Arches: x86_64
Tag options:
tag2distrepo.enabled : 'true'
tag2distrepo.keys : '47dd8ef9'
tag2distrepo.enabled : True
tag2distrepo.keys : '44922a28'
tag2distrepo:skip_missing_signatures : True
To disable the plugin for the same tag:
@ -59,6 +62,6 @@ If you want to create a repository that contains builds signed by more than one
For example:
koji edit-tag smecontribs11 -x tag2distrepo_sme.keys="44922a28 9867c58f 38ab71f4 5323552a"
koji edit-tag smecontribs11 -x tag2distrepo.keys="44922a28 9867c58f 38ab71f4 5323552a"
For each RPM in the tag, Koji will use the first signed copy that it finds. In other words, Koji will try the first key (`44922a28`), and if Koji does not have the first key's signature for that RPM, then it will try the second key (`9867c58f`), third key (`38ab71f4`), and so on.