As 'status' is handled by enable/disable user and user_perms are handled elsewhere, only included renaming and krb_principal here.
Can we get some tests?
@mikem What is your opinion on future use of _dml? Are we going to use Insert/UpdateProcessor where possible, or is it still ok to use _dml for such simple queries?
_dml
Insert/UpdateProcessor
1 new commit added
2 new commits added
Yeah, don't use _dml() in new code if at all possible. There may be exceptions, but this case is clearly a job for UpdateProcessor.
_dml()
UpdateProcessor
rebased onto a83c1d6df50168e5e86d3efe57c2bc68f916746a
:thumbsup: you can also use QueryProcessor here, but it is a simple one.
QueryProcessor
Fixes: https://pagure.io/koji/issue/862
Metadata Update from @breilly: - Pull-request tagged with: testing-ready
I think it's better to use obvious arguments than **kwargs
**kwargs
Metadata Update from @jcupova: - Pull-request tagged with: testing-done
Agreed, that kwargs should be replaced with explicit options.
rebased onto 3bf972668e202d420525137ef7dd03ec1236b907
@julian8628 @tkopecek updated, thanks
Commit be159d7a fixes this pull-request
Pull-Request has been merged by tkopecek
As 'status' is handled by enable/disable user and user_perms are handled elsewhere, only included renaming and krb_principal here.