Scenarios

Real-life, end-to-end workflows - each one a complete story with the personas, the platform behaviour, and final playbooks you can lift into your own automation. If the module reference tells you what each module does, these pages tell you what to build with them. (They are also the few-shot patterns an AI assistant should read before generating NetOrca playbooks.)

The scenarios come from a real deployment: F5 DevCentral's bigip-automation walks the maturity levels of network automation - from imperative scripts (level 1) through per-app Git repos and CI/CD (levels 4-5) to level 6: full lifecycle self-service with NetOrca as the orchestration layer between consumer teams and the BIG-IP team. These pages are level 6, operated with this collection.

Scenario	Persona	You will use	Status
Load balancer as a service - validate, deploy, report; the two scheduled playbooks that run a service	service owner	netorca_change_instance_info, netorca_change_instance, netorca_service_item_info	available
Requesting services from Git - declare in your repo, track your merge to completion	consumer	netorca_change_instance_info, netorca_service_item_info	available
Publishing a service - definition submission, docs, service config	service owner	netorca_service_submission, netorca_service_docs, netorca_service_config	planned - lands with the consumer-flow and config modules
Eventing and health - webhooks on change activity, scheduled healthchecks	service owner	webhook and healthcheck modules	planned - lands with the webhook/healthcheck modules
Billing run - unprocessed charges, reporting, marking processed	service owner	netorca_charge_info, netorca_charge	planned - lands with the charge modules
AI-operated service with Pack - AI renders the config, your executor deploys it, feedback retriggers	service owner	netorca_pack_pipeline_info, netorca_pack_data, netorca_pack_trigger, netorca_ai_processor, netorca_pack_profile	available

The mechanics the scenarios lean on are documented once, in the guides: filtering and pagination, check mode and idempotency (including the change lifecycle state machine), and error handling.