You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The zeebe-client-node library has a "Zero-Conf constructor" that allows to use environment variables to set up Zeebe.
This project could benefit from taking the same approach.
It already supports specifying hostname:port with ZEEBE_ADDRESS.
Describe the solution you'd like
To quote from zeebe-client-node docs:
With no relevant environment variables set, it will default to localhost on the default port with no TLS.
The following environment variable configurations are possible with the Zero-conf constructor:
Having a function that's responsible for loading config and pass it to ZeebeWorker/ZeebeClient on instantiation.
E.g.
zeebe_client=ZeebeClient(**get_zeebe_config())
# where `get_zeebe_config` would return a dict# e.g. {"secure_connection": True, "hostname": "localhost", "port": 26500}
If this is a direction we'd like to take, I'd be happy to submit a PR for this.
The text was updated successfully, but these errors were encountered:
@JonatanMartens I assume #186 was accidentally closed (because the branch it was made against was deleted)? Should I try to rebase this against master/development?
Is your feature request related to a problem? Please describe.
The zeebe-client-node library has a "Zero-Conf constructor" that allows to use environment variables to set up Zeebe.
This project could benefit from taking the same approach.
It already supports specifying
hostname:port
withZEEBE_ADDRESS
.Describe the solution you'd like
To quote from zeebe-client-node docs:
Describe alternatives you've considered
E.g.
If this is a direction we'd like to take, I'd be happy to submit a PR for this.
The text was updated successfully, but these errors were encountered: