Merge pull request #1402 from jumpingliu/issue-1397-main

fix: Replace support-cron-scheduler with support-scheduler

docs_src/api/support/Ch-APISupportScheduler.md

@@ -0,0 +1,7 @@
+# Support Scheduler
+
+EdgeX Foundry's Support Scheduler microservice to schedule actions to occur on specific intervals or crontab definition. See Support Scheduler (TBD) for more details about this service.
+
+## Swagger
+
+<swagger-ui src="https://raw.githubusercontent.com/edgexfoundry/edgex-go/{{edgexversion}}/openapi/support-scheduler.yaml"/>

docs_src/general/ServicePorts.md

@@ -13,8 +13,7 @@ The following tables (organized by type of service) capture the default service
     |Services Name|	Port Definition|
     |---|---|
     |support-notifications	|59860|
-    |support-scheduler|	59861|
-    |support-cron-scheduler|59863|
+    |support-scheduler|	59863|
     |rules engine / eKuiper|59720|
     |system management agent (deprecated)|58890|
 === "Application"

docs_src/microservices/general/index.md

@@ -150,7 +150,7 @@ We have several data models with a timestamp field, but the precision varies, pl
 
 
 [1]: ../core/metadata/ApiReference.md
-[2]: ../support/cronScheduler/ApiReference.md
+[2]: ../support/scheduler/ApiReference.md
 [3]: #service-metrics
 [4]: ../core/metadata/details/DeviceSystemEvents.md#system-event-dto
 [5]: ../../walk-through/Ch-WalkthroughReading.md#origin-timestamp

docs_src/microservices/support/Ch-SupportingServices.md

@@ -9,6 +9,5 @@ These services often need some amount of core services to function.  In all case
 Supporting services include:
 
 - [Rules Engine](./eKuiper/Ch-eKuiper.md):  the reference implementation edge analytics service that performs if-then conditional [actuation](../../general/Definitions.md#actuate) at the edge based on sensor data collected by the EdgeX instance.  Replace or augment this service with use case specific analytics capability.
-- [Support Scheduler](./scheduler/Purpose.md):  an internal EdgeX “clock” that can kick off operations in any EdgeX service.  At a configuration specified time, the service will call on any EdgeX service API URL via REST to trigger an operation.  For example, at appointed times, the scheduler service calls on core data APIs to expunge old sensed events already exported out of EdgeX.
-- [Support Cron Scheduler](./cronScheduler/Purpose.md):  provides a mechanism that can kick off operations in any EdgeX service. At a configuration specified time or a crontab expression scheduled time, the service calls on any EdgeX service via REST, EdgeX Message Bus, or Device Control to trigger an operation.  For example, at appointed times, the scheduler service calls on core data APIs to expunge old sensed events already exported out of EdgeX.
+- [Support Scheduler](./scheduler/Purpose.md):  provides a mechanism that can kick off operations in any EdgeX service. At a configuration specified time or a crontab expression scheduled time, the service calls on any EdgeX service via REST, EdgeX Message Bus, or Device Control to trigger an operation.  For example, at appointed times, the scheduler service calls on core data APIs to expunge old sensed events already exported out of EdgeX.
 - [Support Notifications](./notifications/Purpose.md):  provides EdgeX services with a central facility to send out notifications.  These are notices sent to another system or to a person monitoring the EdgeX instance (internal service communications are often handled more directly).

docs_src/microservices/support/scheduler/ApiReference.md

@@ -0,0 +1,10 @@
+--- 
+title: Support Scheduler - API Reference
+---
+
+# Support Scheduler - API Reference
+
+
+EdgeX Foundry's Support Scheduler microservice schedules actions to occur on specific intervals or a crontab expression scheduled time
+
+<swagger-ui src="https://raw.githubusercontent.com/edgexfoundry/edgex-go/{{edgexversion}}/openapi/support-scheduler.yaml"/>