Bumping the SDK and linting the code

rapid7 · Jan 16, 2025 · 54c0ec4 · 54c0ec4
1 parent 88da607
commit 54c0ec4
Show file tree

Hide file tree

Showing 5 changed files with 8 additions and 7 deletions.
diff --git a/plugins/duo_admin/.CHECKSUM b/plugins/duo_admin/.CHECKSUM
@@ -1,5 +1,5 @@
 {
-	"spec": "95c3a26e6ef8734d0a1abb73a67c12d6",
+	"spec": "814e81dd40fcf4d884c984e0c451201e",
 	"manifest": "b4029998fe0d9bcc85c8016d009d19b3",
 	"setup": "5965f3fd331d7855550e5afad6ea8956",
 	"schemas": [

diff --git a/plugins/duo_admin/Dockerfile b/plugins/duo_admin/Dockerfile
@@ -1,4 +1,4 @@
-FROM --platform=linux/amd64 rapid7/insightconnect-python-3-plugin:6.2.2
+FROM --platform=linux/amd64 rapid7/insightconnect-python-3-plugin:6.2.3
 
 LABEL organization=rapid7
 LABEL sdk=python

diff --git a/plugins/duo_admin/help.md b/plugins/duo_admin/help.md
@@ -950,7 +950,7 @@ Example output:
 
 # Version History
 
-* 5.0.3 - Update Task `monitor_logs` to delay retry if a rate limit error is returned from Duo Admin
+* 5.0.3 - Bump the SDK to version 6.2.3 | Update Task `monitor_logs` to delay retry if a rate limit error is returned from Duo Admin
 * 5.0.2 - Updated SDK to the latest version (v6.2.2) | Address vulnerabilities
 * 5.0.1 - Update to enable Plugin as FedRAMP ready | Update SDK (`6.1.2`)
 * 5.0.0 - Updated to include latest SDK v5.5.5 | Removing Unused fields from User Object

diff --git a/plugins/duo_admin/plugin.spec.yaml b/plugins/duo_admin/plugin.spec.yaml
@@ -11,7 +11,7 @@ status: []
 supported_versions: ["Duo Admin API 2024-09-17"]
 sdk:
   type: full
-  version: 6.2.2
+  version: 6.2.3
   user: nobody
 description: "[Duo](https://duo.com/)'s Trusted Access platform verifies the identity of your users with two-factor authentication and
 security health of their devices before they connect to the apps they use. Using the Duo plugin for InsightConnect will allow Duo user management within automation workflows"
@@ -50,7 +50,7 @@ references:
 troubleshooting:
   - "Many actions in this plugin take a User ID as input. A User ID is not the username - instead it's a unique identifier e.g. DU9I6T0F7R2S1J4XZHHA. A User ID can be obtained by passing a username to the Get User Status action."
 version_history:
-- "5.0.3 - Update Task `monitor_logs` to delay retry if a rate limit error is returned from Duo Admin"
+- "5.0.3 - Bump the SDK to version 6.2.3 | Update Task `monitor_logs` to delay retry if a rate limit error is returned from Duo Admin"
 - "5.0.2 - Updated SDK to the latest version (v6.2.2) | Address vulnerabilities"
 - "5.0.1 - Update to enable Plugin as FedRAMP ready | Update SDK (`6.1.2`)"
 - "5.0.0 - Updated to include latest SDK v5.5.5 | Removing Unused fields from User Object"

diff --git a/plugins/duo_admin/unit_test/test_monitor_logs.py b/plugins/duo_admin/unit_test/test_monitor_logs.py
@@ -106,8 +106,9 @@ def test_monitor_logs(
         self.assertEqual(actual_state, expected.get("state"))
         self.assertEqual(status_code, expected.get("status_code"))
 
-
-    def test_monitor_logs_with_rate_limit_whole_flow(self, mock_request, mock_request_instance, mock_get_headers, mock_get_time):
+    def test_monitor_logs_with_rate_limit_whole_flow(
+        self, mock_request, mock_request_instance, mock_get_headers, mock_get_time
+    ):
         future_time_state = {"rate_limit_datetime": time() + 600}
         passed_time_state = {"rate_limit_datetime": time() - 600}