https://github.com/eodcgmbh/openeo-argoworkflows

Implementation of the openeo api to work with argo workflows
https://github.com/eodcgmbh/openeo-argoworkflows

Last synced: about 1 month ago
JSON representation

Implementation of the openeo api to work with argo workflows

• Host: GitHub
• URL: https://github.com/eodcgmbh/openeo-argoworkflows
• Owner: eodcgmbh
• Created: 2024-06-03T08:15:03.000Z (8 months ago)
• Default Branch: main
• Last Pushed: 2024-12-02T15:02:35.000Z (about 2 months ago)
• Last Synced: 2024-12-02T16:25:20.446Z (about 2 months ago)
• Language: Python
• Size: 5.26 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# OpenEO ArgoWorkflows

OpenEO Argoworkflows is an implementation of the [OpenEO Api]() and [OpenEO Processes]() specifications. This repository implements two components, an api server, and an executor. The Api implementation is based on the [OpenEO Fastapi]() package, and the Executor implementation is based on [OpenEO Processes Dask]() and [OpenEO PG Parser]().

The two components here, are integrated, and expected to be installed via the [OpenEO ArgoWorkflows Helm Chart](). The helm chart a number of dependencies are installed and configured to work with the components implemented here.

## Development

In the respective documentary for the api and executor there is a dockerfile defined that can be used as a development environment for each component.

To work on the Api

```

cd ./openeo_argoworkflows/api

```

To work on the Executor

```

cd ./openeo_argoworkflows/api

```

From each of these directories, there is a .devcontainer configuration. Openining these sub directories in vscode will display the option to open the development container. It is intentional that each of these components have seperate development environments. Source and test code is available in each respective sub repo. **Note**: there are currently no tests for the executor.

## Release

Each component is released using the version number found in its respective pyproject.toml, and prefixed with the name of the component. The version numbers in the toml follow [Calendar Versioning](https://calver.org/) where the Major version is the year, the Minor version the month, and the Mirco version is the index of the release that month, if it is the first release that month, the Micro is 1.

Format:

`( api | executor )-YYYY.MM.MICRO`s