qubership-pipelines-declarative-executor 2.0.0__tar.gz

qubership_pipelines_declarative_executor-2.0.0/LICENSE

@@ -0,0 +1,211 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+
+---
+
+   This product contains parts of the 7-Zip program.
+   7-Zip is free software licensed under the GNU Lesser General Public License (LGPL).
+   You can find the source code for 7-Zip at: https://www.7-zip.org/
+   And license information at https://www.7-zip.org/license.txt
+   Copyright (C) 1999-2024 Igor Pavlov.

qubership_pipelines_declarative_executor-2.0.0/PKG-INFO

@@ -0,0 +1,129 @@
+Metadata-Version: 2.4
+Name: qubership-pipelines-declarative-executor
+Version: 2.0.0
+Summary: Qubership Pipelines Declarative Executor
+License: Apache-2.0
+License-File: LICENSE
+Author: Qubership
+Requires-Python: >=3.11,<4.0
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Dist: PyYAML (>=6.0,<7.0)
+Requires-Dist: aiofiles (>=24.1.0,<25.0.0)
+Requires-Dist: aiohttp (>=3.12.15,<4.0.0)
+Requires-Dist: click (>=8.1,<9.0)
+Requires-Dist: miniopy-async (>=1.23.4,<2.0.0)
+Requires-Dist: requests (>=2.32.3,<3.0.0)
+Description-Content-Type: text/markdown
+
+[![PyPI](https://img.shields.io/pypi/v/qubership-pipelines-declarative-executor)](https://pypi.org/project/qubership-pipelines-declarative-executor/)
+![PyPI - Python Version](https://img.shields.io/pypi/pyversions/qubership-pipelines-declarative-executor)
+![Tests](https://github.com/Netcracker/qubership-pipelines-declarative-executor/actions/workflows/run-tests.yml/badge.svg)
+![Repo Size](https://img.shields.io/github/repo-size/Netcracker/qubership-pipelines-declarative-executor)
+
+# Qubership Pipelines Declarative Executor
+
+Open-source python pipelines orchestrator and executor.
+
+This application is distributed as a library on PyPI, Docker image on GitHub Packages, and as a Reusable Workflow for your existing GitHub workflows.
+You can use this application in any of the provided forms that best suits your needs.
+
+## Structure
+
+### Docker image
+
+Provided Docker image with this application includes:
+
+- Pipelines Declarative Executor app itself
+- [Sample "Python Modules"](https://github.com/Netcracker/qubership-pipelines-cli-command-samples) to execute commands in your "Atlas Pipeline"
+- SOPS binaries to securely process configuration files and output parameters
+
+#### Using your own "Python Modules"
+
+Sample "Python Modules", included in distributed Docker image, are only showcasing the intended way of working via Execution Commands and Execution Context.
+You might need to have your custom commands executed in "Atlas Pipelines" - then you will need to create and distribute your own implementation.
+There's a [Development Guide](https://github.com/Netcracker/qubership-pipelines-cli-command-samples/blob/main/docs/development.md) available in CLI Samples repository.
+
+A few ways you can include your own "Python Modules" into executor Docker image:
+
+- Building new [image](./Dockerfile) with required modules, and putting path to them to `PIPELINES_DECLARATIVE_EXECUTOR_PYTHON_MODULE_PATH` env variable
+- Mounting directory with your modules into the image, while also upgrading `PIPELINES_DECLARATIVE_EXECUTOR_PYTHON_MODULE_PATH` env variable to mounted path
+
+Multiple "Python Modules" are supported via `stage.path` property ([check syntax guide for more information](docs/atlas_pipeline_syntax.md#module-path))
+
+### Python Dependency
+
+You can also use this application as a python dependency, by installing it from PyPI:
+
+```bash
+pip install qubership-pipelines-declarative-executor
+```
+
+Or adding it to your dependency list:
+
+```python
+qubership-pipelines-declarative-executor = "^2.0.0"
+```
+
+### Common CI Workflows (GitHub/GitLab)
+
+Alternative usage scenario (although much less configurable than creating your own workflow, since we can't pass custom env variables into it) is using provided [Reusable Workflow](.github/workflows/reusable-pipeline.yml) in your repository.
+There is an example of how it can be invoked from GitHub Workflow: [pipeline.yml](.github/workflows/pipeline.yml)
+
+There's also an example of a similar implementation [for GitLab](docs/gitlab/.gitlab-ci.yml)
+
+When you've created your own Docker image with necessary "Python Modules" (non-sample ones), you might want to create your own workflows using that image.
+Provided workflows serve as a starting point, but custom workflows will allow full control and ability to pass env variables and local files.
+
+## Features
+
+### Atlas Pipeline definitions
+
+"AtlasPipelines" are intended to work via Execution Commands, packed into ["Python Modules"](https://github.com/Netcracker/qubership-pipelines-cli-command-samples/blob/main/docs/development.md).
+
+Pipeline itself describes data flow between sequentially executed stages, while also supporting invoking nested pipelines (for reusing configuration) and parallel stages.
+
+This repository uses actual "AtlasPipelines" in its tests, you can [check them here](tests/pipeline_configs).
+
+Separate article on syntax with examples [is available here](docs/atlas_pipeline_syntax.md).
+
+### Reporting
+
+Executor collects and can upload report (intended for UI representation) of currently executed pipeline.
+
+This feature is configured via env variables in [Report section](docs/env_vars.md#report-params).
+You can select `REPORT_SEND_MODE` (either `ON_COMPLETION` or `PERIODIC`), send intervals, and endpoint configs:
+
+Report configuration [example is here](docs/config_examples.md#report_remote_endpoints)
+
+### Auth Rules
+
+Orchestrator can fetch remote AtlasPipeline and AtlasConfig files from various sources. To access private repositories or authenticated endpoints, you can configure **authentication rules**.
+
+Example Auth Rules [are present here](docs/config_examples.md#auth_rules)
+
+Rules are processed in order they are defined, and first applicable rule will be used (in case when multiple would've matched).
+
+If no rules match, requests are made without authentication.
+
+### CI Wrapper configuration
+
+You can pass your CI (GitHub, GitLab, Jenkins, etc.) execution instance parameters (user who triggered pipeline, pipeline's URL) to make them available in the report via [environment variables](docs/env_vars.md#executor-wrapper-params)
+
+### SOPS Encryption
+
+Executor decrypts input files (pipelines and configs) if they are encrypted with [SOPS](https://getsops.io/), and can also encrypt any output secure files.
+This feature is configured via a [set of environment variables](docs/env_vars.md#sops-encryption-params)
+
+### ENV Configuration
+
+Other parameters are available and documented in the [General section](docs/env_vars.md#general-params)
+
+### Performance
+
+Performance tests and comparisons of [different ways to invoke imported "Python Modules" will be available here](docs/performance.md)
+

qubership_pipelines_declarative_executor-2.0.0/README.md

@@ -0,0 +1,106 @@
+[![PyPI](https://img.shields.io/pypi/v/qubership-pipelines-declarative-executor)](https://pypi.org/project/qubership-pipelines-declarative-executor/)
+![PyPI - Python Version](https://img.shields.io/pypi/pyversions/qubership-pipelines-declarative-executor)
+![Tests](https://github.com/Netcracker/qubership-pipelines-declarative-executor/actions/workflows/run-tests.yml/badge.svg)
+![Repo Size](https://img.shields.io/github/repo-size/Netcracker/qubership-pipelines-declarative-executor)
+
+# Qubership Pipelines Declarative Executor
+
+Open-source python pipelines orchestrator and executor.
+
+This application is distributed as a library on PyPI, Docker image on GitHub Packages, and as a Reusable Workflow for your existing GitHub workflows.
+You can use this application in any of the provided forms that best suits your needs.
+
+## Structure
+
+### Docker image
+
+Provided Docker image with this application includes:
+
+- Pipelines Declarative Executor app itself
+- [Sample "Python Modules"](https://github.com/Netcracker/qubership-pipelines-cli-command-samples) to execute commands in your "Atlas Pipeline"
+- SOPS binaries to securely process configuration files and output parameters
+
+#### Using your own "Python Modules"
+
+Sample "Python Modules", included in distributed Docker image, are only showcasing the intended way of working via Execution Commands and Execution Context.
+You might need to have your custom commands executed in "Atlas Pipelines" - then you will need to create and distribute your own implementation.
+There's a [Development Guide](https://github.com/Netcracker/qubership-pipelines-cli-command-samples/blob/main/docs/development.md) available in CLI Samples repository.
+
+A few ways you can include your own "Python Modules" into executor Docker image:
+
+- Building new [image](./Dockerfile) with required modules, and putting path to them to `PIPELINES_DECLARATIVE_EXECUTOR_PYTHON_MODULE_PATH` env variable
+- Mounting directory with your modules into the image, while also upgrading `PIPELINES_DECLARATIVE_EXECUTOR_PYTHON_MODULE_PATH` env variable to mounted path
+
+Multiple "Python Modules" are supported via `stage.path` property ([check syntax guide for more information](docs/atlas_pipeline_syntax.md#module-path))
+
+### Python Dependency
+
+You can also use this application as a python dependency, by installing it from PyPI:
+
+```bash
+pip install qubership-pipelines-declarative-executor
+```
+
+Or adding it to your dependency list:
+
+```python
+qubership-pipelines-declarative-executor = "^2.0.0"
+```
+
+### Common CI Workflows (GitHub/GitLab)
+
+Alternative usage scenario (although much less configurable than creating your own workflow, since we can't pass custom env variables into it) is using provided [Reusable Workflow](.github/workflows/reusable-pipeline.yml) in your repository.
+There is an example of how it can be invoked from GitHub Workflow: [pipeline.yml](.github/workflows/pipeline.yml)
+
+There's also an example of a similar implementation [for GitLab](docs/gitlab/.gitlab-ci.yml)
+
+When you've created your own Docker image with necessary "Python Modules" (non-sample ones), you might want to create your own workflows using that image.
+Provided workflows serve as a starting point, but custom workflows will allow full control and ability to pass env variables and local files.
+
+## Features
+
+### Atlas Pipeline definitions
+
+"AtlasPipelines" are intended to work via Execution Commands, packed into ["Python Modules"](https://github.com/Netcracker/qubership-pipelines-cli-command-samples/blob/main/docs/development.md).
+
+Pipeline itself describes data flow between sequentially executed stages, while also supporting invoking nested pipelines (for reusing configuration) and parallel stages.
+
+This repository uses actual "AtlasPipelines" in its tests, you can [check them here](tests/pipeline_configs).
+
+Separate article on syntax with examples [is available here](docs/atlas_pipeline_syntax.md).
+
+### Reporting
+
+Executor collects and can upload report (intended for UI representation) of currently executed pipeline.
+
+This feature is configured via env variables in [Report section](docs/env_vars.md#report-params).
+You can select `REPORT_SEND_MODE` (either `ON_COMPLETION` or `PERIODIC`), send intervals, and endpoint configs:
+
+Report configuration [example is here](docs/config_examples.md#report_remote_endpoints)
+
+### Auth Rules
+
+Orchestrator can fetch remote AtlasPipeline and AtlasConfig files from various sources. To access private repositories or authenticated endpoints, you can configure **authentication rules**.
+
+Example Auth Rules [are present here](docs/config_examples.md#auth_rules)
+
+Rules are processed in order they are defined, and first applicable rule will be used (in case when multiple would've matched).
+
+If no rules match, requests are made without authentication.
+
+### CI Wrapper configuration
+
+You can pass your CI (GitHub, GitLab, Jenkins, etc.) execution instance parameters (user who triggered pipeline, pipeline's URL) to make them available in the report via [environment variables](docs/env_vars.md#executor-wrapper-params)
+
+### SOPS Encryption
+
+Executor decrypts input files (pipelines and configs) if they are encrypted with [SOPS](https://getsops.io/), and can also encrypt any output secure files.
+This feature is configured via a [set of environment variables](docs/env_vars.md#sops-encryption-params)
+
+### ENV Configuration
+
+Other parameters are available and documented in the [General section](docs/env_vars.md#general-params)
+
+### Performance
+
+Performance tests and comparisons of [different ways to invoke imported "Python Modules" will be available here](docs/performance.md)

qubership_pipelines_declarative_executor-2.0.0/pyproject.toml

@@ -0,0 +1,27 @@
+[tool.poetry]
+name = "qubership-pipelines-declarative-executor"
+version = "2.0.0"
+description = "Qubership Pipelines Declarative Executor"
+authors = ["Qubership"]
+readme = "README.md"
+license = "Apache-2.0"
+packages = [{from = "src", include = "pipelines_declarative_executor"}]
+
+[tool.poetry.dependencies]
+python = "^3.11"
+PyYAML = "^6.0"
+click = "^8.1"
+requests = "^2.32.3"
+aiohttp = "^3.12.15"
+aiofiles = "^24.1.0"
+miniopy-async = "^1.23.4"
+
+[tool.poetry.group.test.dependencies]
+pytest = "^6.0.0"
+
+[tool.poetry.scripts]
+pipelines_declarative_executor = "pipelines_declarative_executor.__main__:cli"
+
+[build-system]
+requires = ["poetry-core"]
+build-backend = "poetry.core.masonry.api"

qubership_pipelines_declarative_executor-2.0.0/src/pipelines_declarative_executor/__init__.py

@@ -0,0 +1,3 @@
+import sys, os
+current_path = os.path.dirname(os.path.abspath(__file__))
+sys.path.insert(0, current_path)

qubership_pipelines_declarative_executor-2.0.0/src/pipelines_declarative_executor/__main__.py

@@ -0,0 +1,122 @@
+import sys, asyncio, click, logging
+
+from pipelines_declarative_executor.utils.env_var_utils import EnvVar
+from pipelines_declarative_executor.utils.logging_utils import LoggingUtils
+
+
+@click.group(chain=True)
+def cli():
+    pass
+
+
+@cli.command("run")
+@click.option('--pipeline_data', required=True, type=str, help="Pipeline data (pipeline/config file paths)")
+@click.option('--pipeline_vars', required=False, type=str, help="Pipeline vars with high priority")
+@click.option('--pipeline_dir', required=False, type=str, help="Path to directory where pipeline will be executed")
+@click.option('--is_dry_run', default=False, type=bool, help="Path to directory where pipeline will be executed")
+@click.option('--log_level', default='INFO', show_default=True,
+              type=click.Choice(['DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL'], case_sensitive=False),
+              help="Console logging level")
+def __run_pipeline(pipeline_data: str, pipeline_vars: str, pipeline_dir: str, is_dry_run: bool, log_level: str):
+    LoggingUtils.CONSOLE_LOG_LEVEL = getattr(logging, log_level.upper(), logging.INFO)
+    LoggingUtils.configure_root_logger()
+    logging.info(f'command "RUN" with params:\npipeline_data="{pipeline_data}"\npipeline_vars="{pipeline_vars}"'
+                 f'\npipeline_dir="{pipeline_dir}"\nis_dry_run="{is_dry_run}"\nlog_level="{log_level}"')
+    with (LoggingUtils.time_it(), LoggingUtils.profile_it()):
+        asyncio.run(create_and_run_pipeline(pipeline_data, pipeline_vars, pipeline_dir, is_dry_run))
+
+
+@cli.command("retry")
+@click.option('--pipeline_dir', required=True, type=str, help="Path to directory where pipeline was executed")
+@click.option('--retry_vars', required=False, type=str, help="Retry vars with highest priority")
+@click.option('--log_level', default='INFO', show_default=True,
+              type=click.Choice(['DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL'], case_sensitive=False),
+              help="Console logging level")
+def __retry_pipeline(pipeline_dir: str, retry_vars: str, log_level: str):
+    LoggingUtils.CONSOLE_LOG_LEVEL = getattr(logging, log_level.upper(), logging.INFO)
+    LoggingUtils.configure_root_logger()
+    logging.info(f'command "RETRY" with params:\npipeline_dir="{pipeline_dir}"\nretry_vars="{retry_vars}"'
+                 f'\nlog_level="{log_level}"')
+    with (LoggingUtils.time_it(), LoggingUtils.profile_it()):
+        asyncio.run(retry_pipeline(pipeline_dir, retry_vars))
+
+
+@cli.command("archive")
+@click.option('--pipeline_dir', required=True, type=str, help="Path to directory where pipeline was executed")
+@click.option('--target_path', required=True, type=str, help="Path to resulting archive")
+def __archive_pipeline(pipeline_dir: str, target_path: str):
+    LoggingUtils.configure_root_logger()
+    logging.info(f'command "ARCHIVE" with params:\npipeline_dir="{pipeline_dir}"\ntarget_path="{target_path}"')
+    from pipelines_declarative_executor.utils.archive_utils import ArchiveUtils
+    ArchiveUtils.archive(pipeline_dir, target_path)
+
+
+@cli.command("unarchive")
+@click.option('--archive_path', required=True, type=str, help="Path to archive with pipeline execution")
+@click.option('--target_path', required=True, type=str, help="Path where it will be extracted")
+def __archive_pipeline(archive_path: str, target_path: str):
+    LoggingUtils.configure_root_logger()
+    logging.info(f'command "UNARCHIVE" with params:\narchive_path="{archive_path}"\ntarget_path="{target_path}"')
+    from pipelines_declarative_executor.utils.archive_utils import ArchiveUtils
+    ArchiveUtils.unarchive(archive_path, target_path)
+
+
+async def create_and_run_pipeline(pipeline_data: str, pipeline_vars: str, pipeline_dir: str, is_dry_run: bool):
+    from pipelines_declarative_executor.orchestrator.pipeline_orchestrator import PipelineOrchestrator
+    from pipelines_declarative_executor.executor.pipeline_executor import PipelineExecutor
+    from pipelines_declarative_executor.report.report_uploader import ReportUploader
+    from pipelines_declarative_executor.model.stage import ExecutionStatus
+    try:
+        pipeline_execution = PipelineOrchestrator.prepare_pipeline_execution(
+            pipeline_data=pipeline_data,
+            pipeline_vars=pipeline_vars
+        )
+    except Exception as e:
+        logging.error(f"Exception during orchestration: {e}")
+        sys.exit(1)
+    async with ReportUploader(execution=pipeline_execution, configs=ReportUploader.load_endpoint_configs()):
+        await PipelineExecutor.start(
+            execution=pipeline_execution,
+            execution_folder_path=pipeline_dir,
+            is_dry_run=is_dry_run,
+            wait_for_finish=True,
+        )
+    if pipeline_execution.status != ExecutionStatus.SUCCESS:
+        sys.exit(1)
+
+
+async def retry_pipeline(pipeline_dir: str, retry_vars: str):
+    from pipelines_declarative_executor.orchestrator.retry_orchestrator import PipelineRetryOrchestrator
+    from pipelines_declarative_executor.executor.pipeline_executor import PipelineExecutor
+    from pipelines_declarative_executor.report.report_uploader import ReportUploader
+    from pipelines_declarative_executor.model.stage import ExecutionStatus
+    try:
+        pipeline_execution = PipelineRetryOrchestrator.prepare_retry_execution(
+            pipeline_dir=pipeline_dir,
+            retry_vars=retry_vars,
+        )
+    except Exception as e:
+        logging.error(f"Exception during orchestration: {e}")
+        sys.exit(1)
+    async with ReportUploader(execution=pipeline_execution, configs=ReportUploader.load_endpoint_configs()):
+        await PipelineExecutor.start(
+            execution=pipeline_execution,
+            execution_folder_path=pipeline_dir,
+            is_dry_run=pipeline_execution.is_dry_run,
+            wait_for_finish=True,
+        )
+    if pipeline_execution.status != ExecutionStatus.SUCCESS:
+        sys.exit(1)
+
+
+if __name__ == '__main__':
+    if EnvVar.IS_LOCAL_DEBUG:
+        # local_setup()
+        LoggingUtils.configure_root_logger()
+        logging.debug("=" * 60)
+        logging.warning("RUNNING IN LOCAL DEBUG MODE!")
+        with (LoggingUtils.time_it("Total time"), LoggingUtils.profile_it()):
+            logging.info("Local Debug run")
+            # asyncio.run(local_full_direct_plus_retry())
+    else:
+        cli()

qubership_pipelines_declarative_executor-2.0.0/src/pipelines_declarative_executor/executor/condition_processor.py

@@ -0,0 +1,28 @@
+from pipelines_declarative_executor.model.pipeline import PipelineExecution
+from pipelines_declarative_executor.model.stage import When, ExecutionStatus
+from pipelines_declarative_executor.model.exceptions import PipelineExecutorException
+
+
+class ConditionProcessor:
+    @staticmethod
+    def need_to_execute(execution: PipelineExecution, when: When) -> bool:
+        return ConditionProcessor._check_status(execution, when) and ConditionProcessor._check_condition(execution, when)
+
+    @staticmethod
+    def _check_status(execution: PipelineExecution, when: When) -> bool:
+        is_any_stage_failed = any(stage.status == ExecutionStatus.FAILED for stage in execution.pipeline.stages)
+        return (is_any_stage_failed and ExecutionStatus.FAILED in when.statuses
+                or not is_any_stage_failed and ExecutionStatus.SUCCESS in when.statuses)
+
+    @staticmethod
+    def _check_condition(execution: PipelineExecution, when: When) -> bool:
+        if not when.condition:
+            return True
+        try:
+            condition = execution.vars.calculate_expression(when.condition)
+            result = eval(condition, execution.vars.all_vars())
+            execution.logger.debug(f"Condition ('{condition}') evaluation result: {result if isinstance(result, bool) else result + ' -> ' + bool(result)}")
+            return bool(result)
+        except Exception as e:
+            execution.logger.error(f"Error during calculation of condition - '{when.condition}' - {e}")
+            raise PipelineExecutorException(e)