0
Completed

Allow UNIFYBroker to run as an executable in an environment that doesn't have a console

Adam Bradley 3 years ago updated by Adam van Vliet 3 years ago 5

Service will not run in a Windows Kubernetes container without this capability

Affected Versions:
Fixed by Version:

Answer

Answer
Completed

Will be in the next v5.3 release.

GOOD, I'M SATISFIED
Satisfaction mark by Adam Bradley 3 years ago
Under review

Does the workaround under this answer not work? Happy to investigate, but this might get us going sooner.

Adding Identity Broker as a Windows Service in the Docker Image build is proving challenging. I've only come across documentation on how to start existing services, like the reference you included, and an initial attempt did not prove successful. I'll investigate further but please leave this feature request open. 

Unhandled Exception: System.TypeLoadException: Could not load type 'Unify.Service.ConnectServiceConstants' from assembly 'Unify.Service.Connect, Version=5.3.0.0, Culture=neutral, PublicKeyToken=84b9288cb2633de4'.
   at Unify.Service.Connect.Debug.Program.Main()

Answer
Completed

Will be in the next v5.3 release.