Port config for scheduler is incorrect (59861->59863)

[SynchronicIT]

🐞 Bug Report

Affected Services [REQUIRED]

service-scheduler in edgex-go uses different port number than used in the configure.xml.

Core-Keeper should be able to overrule this based upon the registration of the service, but this doesn't work for the ui.

Is this a regression?

Could be false for a longer time. Not sure as we kicked out Consult and moved to static configuration in the past.

Description and Minimal Reproduction [REQUIRED]

Run the default docker compose examples and check the scheduler in the UI.

🌍 Your Environment

Deployment Environment:

EdgeX Version 4.0: clean installation

[ytakio]

Does anyone know how progress it is? Are there any workaround?

[cloudxxx8]

There is no maintainer of this repository so far

[SynchronicIT]

I don't mind taking up the task as maintainer. As there are more points which we see room for improvement (e.g. ui for core-keeper)

[cloudxxx8]

I believe the first step is to upgrade all the packages / depenedencies.
It's a little outdated.

[lamalexck]

I hacked the configuration file to use port 59863, but I see in the UI.

edgex code: undefined , message: Not Found

Are these still valid?

Registry:
    Host: edgex-core-consul
    Port: 8500
    Type: consul
    ConfigRegistryStem: edgex/
    ServiceVersion: 'v3'
APIGateway:
    Server: edgex-nginx
    ApplicationPort: 8000
    ApplicationPortSSL: 8443

[cloudxxx8]

Registry is not valid, because we drop Consul in v4
This ui is not maintained due to we don't have volunteer or resource