Metadata-Version: 2.4
Name: outsystems-pipeline
Version: 0.10.3
Summary: Python package to accelerate the integration of OutSystems with third-party CI/CD tools
Home-page: https://github.com/OutSystems/outsystems-pipeline
Author: OutSystems
Author-email: cicd.integrations@outsystems.com
License: Apache License 2.0
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: System Administrators
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python
Classifier: Topic :: Software Development :: Build Tools
Classifier: Topic :: Software Development :: Quality Assurance
Classifier: Topic :: Software Development :: Testing
Classifier: Topic :: Software Development :: Testing :: Acceptance
Classifier: Topic :: Software Development :: Testing :: BDD
Classifier: Topic :: Software Development :: Testing :: Unit
Classifier: Topic :: System :: Software Distribution
Requires-Python: >=3.9
License-File: LICENSE
License-File: NOTICE.md
Requires-Dist: python-dateutil==2.9.0.post0
Requires-Dist: requests==2.32.5
Requires-Dist: unittest-xml-reporting==3.2.0
Requires-Dist: xunitparser==1.3.4
Requires-Dist: toposort==1.10
Requires-Dist: python-dotenv==1.0.1
Requires-Dist: packaging==24.1
Dynamic: author
Dynamic: author-email
Dynamic: classifier
Dynamic: description
Dynamic: home-page
Dynamic: keywords
Dynamic: license
Dynamic: license-file
Dynamic: requires-dist
Dynamic: requires-python
Dynamic: summary

The outsystems-pipeline Python package provides functions to support the creation of OutSystems CI/CD pipelines using your DevOps automation tool of choice.

Visit the `project repository <https://github.com/OutSystems/outsystems-pipeline>`_ on GitHub for instructions on how to build example OutSystems CI/CD pipelines with common DevOps automation tools, as well as documentation that will help you adapt the examples to your particular scenarios.


What's new
==========

**Continue Deployment (Two Stage)**

 The following script has a new optional parameter to specify a deployment plan key to continue:

 * `continue_deployment_to_target_env.py`

**Pipeline Cache Information**

 Every time a script creates a new deployment plan, it generates a cache file containing the deployment key.
 This file is stored in the artifact folder and named `<environment_name>_deployment_key.cache`, where `<environment_name>` is the name of the target environment as defined in LifeTime.

Installing and upgrading
========================

Install or upgrade outsystems-pipeline to the latest available version as follows:
::

    pip install -U outsystems-pipeline

