Add a new hub method for inserting new archivetype records.
This closely matches addBType.
The purpose of this change is to make it easier to permit content
generators to import files with extensions that we have not defined in
the upstream packaged koji SQL file.
Some files in the tree had bits of code that you could run if you
executed the files directly as scripts. Now that we have unit tests and
the "fakehub" tool, we do not need this code.
Koji was using the array_remove() SQL function, which was not introduced
until Postgres 9.4. RHEL 7 ships with Postgres 9.2. This construct
was being used to ensure that the krb_principals arrays in user
dictionaries were empty if no principals were defined, instead of
having a single value of None. Instead we use QueryProcessor's result
transformation support to remove the None entry.
Signed-off-by: Jim Foraker <foraker1@llnl.gov>
The recent changes to kerberos principal handling broke proper reporting
of package ownership, due to an obvious typo.
Signed-off-by: Jim Foraker <foraker1@llnl.gov>
Add a new hub method for listing new content generator records.
The purpose of this change is to make it easier for administrators to
determine what content generators are present and what user accounts
have access to those.
With mod_python we could use Apache's PythonOption directive. That
directive does not exist with mod_wsgi and we have to use SetEnv
instead.
Remove the PythonOption directive and describe how to use SetEnv.
Changing owner is triggering repo regeneration in kojira. As it is
something which doesn't have any effect on repodata, let's put it to
separate table and let kojira ignore these changes.
Fixes: https://pagure.io/koji/issue/956
randint's top limit is included in range, so original value 256 can be
reached and as such hex-digit 100 is emitted enlarging the string.
Fixes: https://pagure.io/koji/issue/1611
