How to overwrite the intervaltime in support-scheduler?

[bighb69738]

I tried to overwrite interval time

configuration.yaml

ScheduleIntervalTime: 500
Writable:
    LogLevel: INFO
Service:
    Host: localhost
    Port: 59861
    StartupMsg: "This is the Support Scheduler Microservice"
Intervals:
    Midnight:
        Name: midnight
        Start: 20180101T000000
        Interval: 2h
    Fiveminutes:
        Name: 5m
        Start: 20180101T000000
        Interval: 5m
IntervalActions:
    ScrubAged:
        Name: scrub-aged-events
        Host: localhost
        Port: 59880
        Protocol: http
        Method: DELETE
        Path: /api/v3/event/age/604800000000000   # Remove events older than 7 days
        Interval: midnight
        AdminState: UNLOCKED
        AuthMethod: JWT     # AuthMethod = JWT degrades to no auth in security-disabled EdgeX

MessageBus:
  Optional:
    ClientId: support-scheduler

Database:
  Name: scheduler

docker-compose

support-scheduler:
   ...
    volumes:
    - type: bind
      source: /etc/localtime
      target: /etc/localtime
      bind:
        create_host_path: true
    - type: volume
      source: ./res/support-scheduler
      target: /res

But it does not change on dashboard

[cloudxxx8]

You can control it through the API call
https://docs.edgexfoundry.org/3.1/api/support/Ch-APISupportScheduler/

[lenny-goodell]

@bighb69738 , the configuration file is only used on the first start of the service, which pushes the configuration into the config provider (aka Consul). On subsequent restarts, it pulls the configuration from the Config provider, so your changes will not be seen since you had started the service with the original configuration which is being pulled from Consul. Also not that the configuration is used to create the Intervals in the DB.

There are 4 ways to resolve this:

1. Do a clean stop of all services and then a fresh start with your volume mounted configuration.
2. Delete the configuration from Consul using Consul UI at http://localhost:8500/ui/dc1/kv/edgex/v3 and restart the service
   • Delete the support-scheduler node
   • Note that this will only create the new Interval. The existing interval already exists in the DB and is not changed.
3. Make the changes from the Consul UI at http://localhost:8500/ui/dc1/kv/edgex/v3/support-scheduler/Intervals/ instead of volume mounting custom config file.
   • Must restart the service after the changes are made
   • Note that this will only create the new Interval. The existing interval already exists in the DB and is not changed
4. Uses @cloudxxx8 recommendation to use the REST API to make changes to existing and add new Intervals.
   • Note that they existing IntrevalAction must be removed removed or modified to not use the existing Interval before the Interval can be modified.
   • Note this can also be done via the EdgeX UI