fix: usage example

Author: syedhaseebahmed

workflows/argo-events/cronworkflows/resync-nautobot.yaml

@@ -4,13 +4,13 @@ kind: CronWorkflow
 metadata:
   name: resync-nautobot
   annotations:
-    workflows.argoproj.io/title: Scheduled resync of Keystone and Ironic to Nautobot
+    workflows.argoproj.io/title: Scheduled resync of Keystone, Neutron and Ironic to Nautobot
     workflows.argoproj.io/description: |
-      Periodically resyncs Keystone projects and Ironic nodes to Nautobot to
-      catch any drift. Runs daily at 2:00 AM UTC by default.
+      Periodically resyncs Keystone projects, Neutron networks, subnets and Ironic nodes
+      and ports to Nautobot to catch any drift. Runs daily at 2:00 AM UTC by default.
 
       Keystone projects are synced first (tenants must exist before devices can
-      reference them), then Ironic nodes.
+      reference them), then Neutron networks, subnets, then Ironic nodes.
 
       To manually trigger:
       ```

workflows/argo-events/workflowtemplates/resync-nautobot.yaml

@@ -12,17 +12,11 @@ metadata:
       devices can reference them), then Neutron networks, then Ironic nodes.
       Each step continues even if the previous step fails.
 
-      To resync all:
+      Usage:
       ```
       argo -n argo-events submit --from workflowtemplate/resync-nautobot
       ```
 
-      To resync specific items:
-      ```
-      argo -n argo-events submit --from workflowtemplate/resync-nautobot \
-        -p project="<project-uuid>" -p node="<node-uuid>"
-      ```
-
       Defined in `workflows/argo-events/workflowtemplates/resync-nautobot.yaml`
 spec:
   entrypoint: main