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
Entries defined via command line arguments and in the ocnfig file would all be used, with those in the command line taking precedence in case of duplicate local port entries.
Incorrectly formatted entries would be discarded and a warning logged.
What are the expected benefits and drawbacks?
This will make scripting the tool much easier, and allow easier integration in automated processes.
Are you foreseeing any hurtles or drawbacks?
No
The text was updated successfully, but these errors were encountered:
What is your idea?
Currently the configuration of the port forwarding is done in a properties file, with entries of type
forwarder4j.service.<local_port> = <host>:<port>
It would be nice to be able to also define entries through command line arguments, for instance:
Entries defined via command line arguments and in the ocnfig file would all be used, with those in the command line taking precedence in case of duplicate local port entries.
Incorrectly formatted entries would be discarded and a warning logged.
What are the expected benefits and drawbacks?
This will make scripting the tool much easier, and allow easier integration in automated processes.
Are you foreseeing any hurtles or drawbacks?
No
The text was updated successfully, but these errors were encountered: