feat: GeoZarr pipeline with STAC registration and augmentation #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add complete Argo Workflows infrastructure for geozarr pipeline with automated AMQP event triggering. Workflow pipeline: - Convert: Sentinel-2 Zarr → GeoZarr (cloud-optimized) - Register: Create STAC item with metadata - Augment: Add visualization links (XYZ tiles, TileJSON) Event-driven automation: - AMQP EventSource subscribes to RabbitMQ queue - Sensor triggers workflows on incoming messages - RBAC configuration for secure execution Configuration: - Python dependencies (pyproject.toml, uv.lock) - Pre-commit hooks (ruff, mypy, yaml validation) - TTL cleanup (24h auto-delete completed workflows)
wietzesuijker
force-pushed
the
feature/geozarr-pipeline
branch
5 times, most recently
from
678ebd6 to
d25b852
Compare
Add STAC registration, augmentation, and workflow submission scripts. - register_stac.py: Create/update STAC items with S3→HTTPS rewriting - augment_stac_item.py: Add visualization links (XYZ tiles, TileJSON) - submit_via_api.py: Submit workflows via Argo API for testing - Retry with exponential backoff on transient failures - Configurable timeouts via HTTP_TIMEOUT, RETRY_ATTEMPTS, RETRY_MAX_WAIT - Workflow step timeouts: 1h convert, 5min register/augment
Add operator notebooks and environment configuration. - Submit workflow examples (AMQP and direct API) - Environment variable template (.env.example) - .gitignore for Python, IDEs, Kubernetes configs
Add container build configuration and development tooling. - Dockerfile for data-pipeline image - Makefile for common tasks (build, push, test) - GitHub Container Registry integration
Add comprehensive testing and project documentation. - Unit tests for register_stac and augment_stac_item - Integration tests for workflow submission - E2E test configuration - Project README, CONTRIBUTING, QUICKSTART guides - CI workflow (GitHub Actions)
wietzesuijker
force-pushed
the
feature/geozarr-pipeline
branch
from
d25b852 to
d52e21e
Compare
wietzesuijker
added a commit
that referenced
this pull request
Oct 14, 2025
Replace logger.error() calls with logger.exception() to capture full stack
traces in production Kubernetes logs. Adds structured context via extra={}
for improved observability:
- load_payload: Include file path on FileNotFoundError/JSONDecodeError
- format_routing_key: Show template and available fields on KeyError
- main: Include exchange/routing_key/host on publish failure
Closes phase3-analysis #1 (error logging completion)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Split into 5 stacked PRs for review.
Sequential PRs
Review and merge in order:
infrastructure: feat: argo workflow orchestration and dependencies #2 ← Start here
scripts: feat: pipeline scripts #3 (depends on infrastructure)
examples-notebooks: docs: examples and configuration #4 (depends on scripts)
build: build: Docker images and Makefile #5 (depends on examples-notebooks)
testing: test: test suite and documentation #6 (depends on build)
How stacked PRs work
Architecture
Reliability Features
Testing
✅ Tests passing
✅ E2E workflow validated
✅ Pre-commit hooks passing
Note: This PR (#1) remains open for tracking. Please review and merge the 5 linked PRs above sequentially.