Add documentation for TaskGroup

closes: #6641
https://pulp.plan.io/issues/6641

CHANGES/6641.doc

@@ -0,0 +1 @@
+Add some documentation around TaskGroups.

docs/plugins/plugin-writer/concepts/index.rst

@@ -69,6 +69,14 @@ Tasks are deployed from Views or Viewsets, please see :ref:`kick-off-tasks`.
    tasks/export
 
 
+**Task Groups**
+
+Sometimes you may want to create many tasks to perform different parts of one larger piece of work,
+but you need a simple means to track the progress of these many tasks. Task Groups serve this purpose
+by providing details on the number of associated tasks in each possible state. For more details,
+please see :ref:`kick-off-tasks`.
+
+
 Sync Pipeline
 -------------
 
@@ -78,6 +86,8 @@ Sync Pipeline
    sync_pipeline/sync_pipeline
 
 
+.. _content-protection:
+
 Content Protection
 ------------------
 

docs/plugins/plugin-writer/concepts/subclassing/viewsets.rst

@@ -62,6 +62,8 @@ Kick off Tasks
 Some endpoints may need to deploy tasks to the tasking system. The following is an example of how
 this is accomplished.
 
+See :class:`~pulpcore.plugin.tasking.enqueue_with_reservation` for more details.
+
 .. code-block:: python
 
         # We recommend using POST for any endpoints that kick off task.
@@ -92,7 +94,12 @@ this is accomplished.
             # Since tasks are asynchronous, we return a 202
             return OperationPostponedResponse(result, request)
 
-See :class:`~pulpcore.plugin.tasking.enqueue_with_reservation` for more details.
+If a "task_group" is provided as an optional keyword argument, then the deployed task will be
+automatically added to the task group. Once done spawning new tasks for a given task group,
+you should call ``.finish()`` on the task group object.
+
+For more details about the reservation system and task groups, see :ref:`writing-tasks`. and
+:class:`~pulpcore.plugin.models.TaskGroup`.
 
 
 Content Upload ViewSet