feat: migrate orchestration layer to Kestra #27
Reference in New Issue
Block a user
Delete Branch "feat/kestra-orchestration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
This PR migrates the orchestration layer from a custom Python asyncio/Redis architecture to Kestra, a modern workflow orchestration platform.
Why Kestra?
Changes
README Updated
Issues Updated
Closed (replaced by Kestra native features):
Adapted for Kestra:
fabric-reconcile.ymlworkflowdrift-remediation.ymlworkflowNew issues created:
New Architecture
What's Preserved
src/netbox/- NetBox client and Pydantic modelssrc/gnmi/- gNMI client wrappersrc/yang/- YANG path mappingssrc/cli.py- Discovery commands (fabric-orch discover)docs/Next Steps
After merging, the following issues should be tackled in order:
fabric-reconcile.ymlworkflowChecklist