devsecops-engine-tools 1.175.1__tar.gz → 1.176.0__tar.gz

{devsecops_engine_tools-1.175.1 → devsecops_engine_tools-1.176.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devsecops-engine-tools
-Version: 1.175.1
+Version: 1.176.0
 Summary: Tool for DevSecOps strategy
 Home-page: https://github.com/bancolombia/devsecops-engine-tools
 Author: Bancolombia DevSecOps Team
@@ -24,7 +24,7 @@ Requires-Dist: PyGithub==2.8.1
 Requires-Dist: distro==1.9.0
 Requires-Dist: boto3==1.40.70
 Requires-Dist: docker==7.1.0
-Requires-Dist: setuptools==83.0.0
+Requires-Dist: setuptools==84.1.0
 Requires-Dist: rich==14.1.0
 Requires-Dist: cpe==1.3.1
 Requires-Dist: packageurl-python==0.13.4
@@ -74,6 +74,22 @@ Here are the channels we use to communicate about the project:
 
 Please follow our [Getting Started Guide](https://bancolombia.github.io/devsecops-engine-tools/)
 
+## Scan exit codes
+
+The `devsecops-engine-tools` command and the Python module entry point return:
+
+- `0` when the execution finishes without a failed pipeline result. Warnings
+  (`succeeded_with_issues`), excluded findings, skipped scans, and modules in
+  maintenance do not cause a nonzero exit code.
+- `1` when any scan policy declares the pipeline result as `failed`, including
+  vulnerability severity or priority thresholds, blocked CVEs, compliance
+  thresholds, and risk policies. Execution errors also return `1`.
+
+This applies to `--platform_devops azure`, `github`, and `local`, preserving each
+platform's existing result messages and policy rules. A later successful result
+does not clear an earlier failure. Reporting and enabled metrics finish before
+the command returns the policy failure exit code.
+
 # How can I help?
 
 Review the issues, we hear new ideas. Read more [Contributing](https://github.com/bancolombia/devsecops-engine-tools/blob/trunk/docs/CONTRIBUTING.md)

{devsecops_engine_tools-1.175.1 → devsecops_engine_tools-1.176.0}/devsecops_engine_tools/engine_core/src/applications/runner_engine_core.py

@@ -332,7 +332,7 @@ def get_inputs_from_cli(args):
     }
 
 
-def application_core():
+def application_core() -> int:
     tb = True
     devops_platform_gateway = None
     try:
@@ -383,19 +383,22 @@ def application_core():
             license_tool_gateway,
             args
         )
+        return devops_platform_gateway.exit_code
 
     except Exception as e:
         error_msg = ""
         if tb: error_msg = " | " + traceback.format_exc().replace("\n", " | ")
 
         logger.error("Error engine_core: {0} ".format(str(e)))
-        print(
-            devops_platform_gateway.message(
-                "error", "Error engine_core: {0}{1}".format(str(e), error_msg)
+        if devops_platform_gateway is not None:
+            print(
+                devops_platform_gateway.message(
+                    "error", "Error engine_core: {0}{1}".format(str(e), error_msg)
+                )
             )
-        )
-        print(devops_platform_gateway.result_pipeline("failed"))
+            print(devops_platform_gateway.result_pipeline("failed"))
+        return 1
 
 
 if __name__ == "__main__":
-    application_core()
+    sys.exit(application_core())

{devsecops_engine_tools-1.175.1 → devsecops_engine_tools-1.176.0}/devsecops_engine_tools/engine_core/src/domain/model/gateway/devops_platform_gateway.py

@@ -1,7 +1,11 @@
 from abc import ABCMeta, abstractmethod
+from dataclasses import dataclass, field
 
 
+@dataclass
 class DevopsPlatformGateway(metaclass=ABCMeta):
+    exit_code: int = field(default=0, init=False)
+
     @abstractmethod
     def get_remote_config(self, repository, path, branch):
         "get_remote_config"

{devsecops_engine_tools-1.175.1 → devsecops_engine_tools-1.176.0}/devsecops_engine_tools/engine_core/src/infrastructure/driven_adapters/azure/azure_devops.py

@@ -55,6 +55,7 @@ class AzureDevops(DevopsPlatformGateway):
 
     def result_pipeline(self, type):
         if type == "failed":
+            self.exit_code = 1
             return AzureMessageResultPipeline.Failed.value
         elif type == "succeeded":
             return AzureMessageResultPipeline.Succeeded.value

{devsecops_engine_tools-1.175.1 → devsecops_engine_tools-1.176.0}/devsecops_engine_tools/engine_core/src/infrastructure/driven_adapters/github/github_actions.py

@@ -52,6 +52,8 @@ class GithubActions(DevopsPlatformGateway):
         return formats.get(type, message)
 
     def result_pipeline(self, type):
+        if type == "failed":
+            self.exit_code = 1
         results = {
             "failed": f"{self.FAIL}{self.ICON_FAIL}Failed{self.ENDC}",
             "succeeded": f"{self.OKGREEN}{self.ICON_SUCCESS}Succeeded{self.ENDC}",

{devsecops_engine_tools-1.175.1 → devsecops_engine_tools-1.176.0}/devsecops_engine_tools/engine_core/src/infrastructure/driven_adapters/runtime_local/runtime_local.py

@@ -36,6 +36,7 @@ class RuntimeLocal(DevopsPlatformGateway):
 
     def result_pipeline(self, type):
         if type == "failed":
+            self.exit_code = 1
             return f"{self.FAIL}{self.ICON_FAIL}Failed{self.ENDC}"
         elif type == "succeeded":
             return f"{self.OKGREEN}{self.ICON_SUCCESS}Succeeded{self.ENDC}"

devsecops_engine_tools-1.176.0/devsecops_engine_tools/version.py

@@ -0,0 +1 @@
+version = '1.176.0'

{devsecops_engine_tools-1.175.1 → devsecops_engine_tools-1.176.0}/devsecops_engine_tools.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devsecops-engine-tools
-Version: 1.175.1
+Version: 1.176.0
 Summary: Tool for DevSecOps strategy
 Home-page: https://github.com/bancolombia/devsecops-engine-tools
 Author: Bancolombia DevSecOps Team
@@ -24,7 +24,7 @@ Requires-Dist: PyGithub==2.8.1
 Requires-Dist: distro==1.9.0
 Requires-Dist: boto3==1.40.70
 Requires-Dist: docker==7.1.0
-Requires-Dist: setuptools==83.0.0
+Requires-Dist: setuptools==84.1.0
 Requires-Dist: rich==14.1.0
 Requires-Dist: cpe==1.3.1
 Requires-Dist: packageurl-python==0.13.4
@@ -74,6 +74,22 @@ Here are the channels we use to communicate about the project:
 
 Please follow our [Getting Started Guide](https://bancolombia.github.io/devsecops-engine-tools/)
 
+## Scan exit codes
+
+The `devsecops-engine-tools` command and the Python module entry point return:
+
+- `0` when the execution finishes without a failed pipeline result. Warnings
+  (`succeeded_with_issues`), excluded findings, skipped scans, and modules in
+  maintenance do not cause a nonzero exit code.
+- `1` when any scan policy declares the pipeline result as `failed`, including
+  vulnerability severity or priority thresholds, blocked CVEs, compliance
+  thresholds, and risk policies. Execution errors also return `1`.
+
+This applies to `--platform_devops azure`, `github`, and `local`, preserving each
+platform's existing result messages and policy rules. A later successful result
+does not clear an earlier failure. Reporting and enabled metrics finish before
+the command returns the policy failure exit code.
+
 # How can I help?
 
 Review the issues, we hear new ideas. Read more [Contributing](https://github.com/bancolombia/devsecops-engine-tools/blob/trunk/docs/CONTRIBUTING.md)

{devsecops_engine_tools-1.175.1 → devsecops_engine_tools-1.176.0}/devsecops_engine_tools.egg-info/requires.txt

@@ -12,7 +12,7 @@ PyGithub==2.8.1
 distro==1.9.0
 boto3==1.40.70
 docker==7.1.0
-setuptools==83.0.0
+setuptools==84.1.0
 rich==14.1.0
 cpe==1.3.1
 packageurl-python==0.13.4

devsecops_engine_tools-1.175.1/devsecops_engine_tools/version.py

@@ -1 +0,0 @@
-version = '1.175.1'