Merge branch 'master' into release-1.1.0

.github/FUNDING.yml

@@ -0,0 +1,14 @@
+# These are supported funding model platforms
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: # Replace with a single Buy Me a Coffee username
+thanks_dev: # Replace with a single thanks.dev username
+custom: ["https://openwisp.org/sponsorship/"]

.github/workflows/pypi.yml

@@ -0,0 +1,32 @@
+name: Publish Python Package to Pypi.org
+
+on:
+  release:
+    types: [published, edited]
+
+permissions:
+  id-token: write
+
+jobs:
+  pypi-publish:
+    name: Release Python Package on Pypi.org
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/openwisp-controller
+    permissions:
+      id-token: write
+    steps:
+    - uses: actions/checkout@v4
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: '3.10'
+    - name: Install dependencies
+      run: |
+        pip install -U pip
+        pip install build
+    - name: Build package
+      run: python -m build
+    - name: Publish package distributions to PyPI
+      uses: pypa/[email protected]

docs/developer/utils.rst

@@ -146,6 +146,55 @@ object are changed, but only on ``post_add`` or ``post_remove`` actions,
 ``post_clear`` is ignored for the same reason explained in the previous
 section.
 
+``config_deactivating``
+~~~~~~~~~~~~~~~~~~~~~~~
+
+**Path**: ``openwisp_controller.config.signals.config_deactivating``
+
+**Arguments**:
+
+- ``instance``: instance of the object being deactivated
+- ``previous_status``: previous status of the object before deactivation
+
+This signal is emitted when a configuration status of device is set to
+``deactivating``.
+
+``config_deactivated``
+~~~~~~~~~~~~~~~~~~~~~~
+
+**Path**: ``openwisp_controller.config.signals.config_deactivated``
+
+**Arguments**:
+
+- ``instance``: instance of the object being deactivated
+- ``previous_status``: previous status of the object before deactivation
+
+This signal is emitted when a configuration status of device is set to
+``deactivated``.
+
+``device_deactivated``
+~~~~~~~~~~~~~~~~~~~~~~
+
+**Path**: ``openwisp_controller.config.signals.device_deactivated``
+
+**Arguments**:
+
+- ``instance``: instance of the device being deactivated
+
+This signal is emitted when a device is flagged for deactivation.
+
+``device_activated``
+~~~~~~~~~~~~~~~~~~~~
+
+**Path**: ``openwisp_controller.config.signals.device_activated``
+
+**Arguments**:
+
+- ``instance``: instance of the device being activated
+
+This signal is emitted when a device is flagged for activation (after
+deactivation).
+
 .. _config_backend_changed:
 
 ``config_backend_changed``

docs/index.rst

@@ -35,6 +35,7 @@ the OpenWISP architecture.
     :maxdepth: 1
 
     user/intro.rst
+    user/device-config-status.rst
     user/templates.rst
     user/variables.rst
     user/device-groups.rst

docs/user/device-config-status.rst

@@ -0,0 +1,38 @@
+Device Configuration Status
+===========================
+
+The device's configuration status (`Device.config.status`) indicates the
+current state of the configuration as managed by OpenWISP. The possible
+statuses and their meanings are explained below.
+
+``modified``
+------------
+
+The device configuration has been updated in OpenWISP, but these changes
+have not yet been applied to the device. The device is pending an update.
+
+``applied``
+-----------
+
+The device has successfully applied the configuration changes made in
+OpenWISP. The current configuration on the device matches the latest
+changes.
+
+``error``
+---------
+
+An issue occurred while applying the configuration to the device, causing
+the device to revert to its previous working configuration.
+
+``deactivating``
+----------------
+
+The device is in the process of being deactivated. The configuration is
+scheduled to be removed from the device.
+
+``deactivated``
+---------------
+
+The device has been deactivated. The configuration applied through
+OpenWISP has been removed, and any other operation to manage the device
+will be prevented or rejected.

docs/user/rest-api.rst

@@ -233,10 +233,29 @@ from the config of a device,
 Delete Device
 ~~~~~~~~~~~~~
 
+.. note::
+
+    A device must be deactivated before it can be deleted. Otherwise, an
+    ``HTTP 403 Forbidden`` response will be returned.
+
 .. code-block:: text
 
     DELETE /api/v1/controller/device/{id}/
 
+Deactivate Device
+~~~~~~~~~~~~~~~~~
+
+.. code-block:: text
+
+    POST /api/v1/controller/device/{id}/deactivate/
+
+Activate Device
+~~~~~~~~~~~~~~~
+
+.. code-block:: text
+
+    POST /api/v1/controller/device/{id}/activate/
+
 List Device Connections
 ~~~~~~~~~~~~~~~~~~~~~~~
 

docs/user/settings.rst

@@ -76,7 +76,7 @@ ways in which OpenWISP can connect to devices in order to launch commands.
 ``OPENWISP_UPDATE_STRATEGIES``
 ------------------------------
 
-============ ============================================================================
+============ ==============================================================================
 **type**:    ``tuple``
 **default**: .. code-block:: python
 
@@ -85,8 +85,12 @@ ways in which OpenWISP can connect to devices in order to launch commands.
                          "openwisp_controller.connection.connectors.openwrt.ssh.OpenWrt",
                          "OpenWRT SSH",
                      ),
+                     (
+                         "openwisp_controller.connection.connectors.openwrt.ssh.OpenWisp1",
+                         "OpenWISP 1.x SSH",
+                     ),
                  )
-============ ============================================================================
+============ ==============================================================================
 
 Available update strategies. An update strategy is a subclass of a
 connector class which defines an ``update_config`` method which is in