You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2024. It is now read-only.
Florian Sellmayr edited this page Oct 22, 2016
·
2 revisions
Accessing State
The current and past state of pipelines and their structure can be accessed through the functions in lambdacd.state.core. This namespace provides a stable, easy to use wrapper around the functionalities of the pipeine state component. For details, see the inline docstrings in the code.
Implementing custom storage
By default, LambdaCD saves the history of pipeline-runs on disk in the LambdaCD home-dir (see Configuration). This behaviour can be replaced by implementing a custom pipeline state component and passing it to assemble-pipeline as an additional parameter. For example, SimonMonecke created an implementation saving state in MongoDB
To create a custom pipeline state component, implement the protocols in lambdacd.state.protocols.