Learn more about these different git repos.
Other Git URLs
When the database for hub will run on an central database server, then the hub will try always to connect to it without ssl encryption. So the database server will reject the connection. I have try to add an dirty hack to the python lib for the database connection. Then the connection will work, but not local databases will don't work any more. So it must be implemented as an option, but I don'*t know the code in detail to write an pull request. So I simple add the bugzilla link where I noted what I have done.
Oh the missing Bugzilla URL https://bugzilla.redhat.com/show_bug.cgi?id=1954590
Metadata Update from @tkopecek: - Custom field Size adjusted to None - Issue set to the milestone: 1.26
I like how psycopg2 passes options directly through to libpq. https://www.psycopg.org/docs/module.html
I wonder if we could expose that in the Koji hub configuration somehow, so we don't have to keep adding options into Koji one-by-one. Then we would get "sslmode" for free (and "sslrootcert", "sslcrl", plus the kerberos options, etc), and as long as psycopg2 / libpq support it, Koji would support it also.
Metadata Update from @tkopecek: - Issue set to the milestone: 1.27 (was: 1.26)
PR 2957
Metadata Update from @jcupova: - Issue set to the milestone: 1.26 (was: 1.27)
Metadata Update from @tkopecek: - Issue set to the milestone: 1.27 (was: 1.26) - Issue tagged with: testing-ready
Metadata Update from @jcupova: - Issue untagged with: testing-ready
new PR 2958
Commit dfce69f fixes this issue
Commit 44c89e3 fixes this issue
Metadata Update from @tkopecek: - Issue set to the milestone: 1.26 (was: 1.27)
Metadata Update from @jcupova: - Issue tagged with: testing-done, testing-ready
Login to comment on this ticket.