Skip to content

Commit c70796f

Browse files
docs: document how to use sudo if modifying an object
Add a warning about using `sudo` when saving. Give an example of how to `get` an object, modify it, and then `save` it using `sudo` Closes: #532
1 parent 6fedfa5 commit c70796f

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

docs/api-usage.rst

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -411,6 +411,27 @@ user. For example:
411411
412412
p = gl.projects.create({'name': 'awesome_project'}, sudo='user1')
413413
414+
.. warning::
415+
When using ``sudo``, its usage is not remembered. What this means is that if
416+
you use ``sudo`` to retrieve an object and then later use ``save()`` to
417+
modify the object it will not use ``sudo``. In that case you should do
418+
``save(sudo='user1')``
419+
420+
Updating with ``sudo``
421+
----------------------
422+
423+
An example of how to ``get`` an object (using ``sudo``), modify the object, and
424+
then ``save`` the object (using ``sudo``)
425+
426+
.. code-block:: python
427+
428+
group = gl.groups.get('example-group')
429+
notification_setting = group.notificationsettings.get(sudo='user1')
430+
notification_setting.level = gitlab.const.NOTIFICATION_LEVEL_GLOBAL
431+
# Must use `sudo` again when doing the save.
432+
notifcation_setting.save(sudo='user1')
433+
434+
414435
Logging
415436
=======
416437

0 commit comments

Comments
 (0)