Fix for issue #10207 non-existent env import (#11053)

* get or create environment * honor auto_create_context, update docs * case of not providing environment * create base class, re-use code import, reimport * put common context code in base * mistyped dict for data
DefectDojo · Oct 19, 2024 · c310a1f · c310a1f
1 parent 05faab6
commit c310a1f
Show file tree

Hide file tree

Showing 2 changed files with 89 additions and 264 deletions.
diff --git a/docs/content/en/integrations/importing.md b/docs/content/en/integrations/importing.md
@@ -69,7 +69,7 @@ An import can be performed by specifying the names of these entities in the API
 }
 ```
 
-When `auto_create_context` is `True`, the product and engagement will be created if needed. Make sure your user has sufficient [permissions](../usage/permissions) to do this.
+When `auto_create_context` is `True`, the product, engagement, and environment will be created if needed. Make sure your user has sufficient [permissions](../usage/permissions) to do this.
 
 A classic way of importing a scan is by specifying the ID of the engagement instead:
-Original file line number
+Diff line change
@@ Expand Up @@
     }
     ```
-    When `auto_create_context` is `True`, the product and engagement will be created if needed. Make sure your user has sufficient [permissions](../usage/permissions) to do this.
+    When `auto_create_context` is `True`, the product, engagement, and environment will be created if needed. Make sure your user has sufficient [permissions](../usage/permissions) to do this.
     A classic way of importing a scan is by specifying the ID of the engagement instead:
@@ Expand Down @@