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
Slice flags seem to have somewhat counter-intuitive behavior (or at least not specifiable).
I want to specify a default slice which is a known safe (or failsafe), but also want to allow the user to override it and specify a whole bunch of elements.
But if I do something like this:
cli.StringSliceFlag {
Name: "management-socket",
Value: &cli.StringSlice{"unix:///var/run/log_processor.socket",},
Usage: "Sockets (unix:// or tcp://) on which to serve the management interface",
},
Then what I get instead is that when I specify a command line option for that parameter - i.e. --management-socket tcp://0.0.0.0:8080 then that just gets appended to the default slice, rather then replacing it.
The text was updated successfully, but these errors were encountered:
Slice flags seem to have somewhat counter-intuitive behavior (or at least not specifiable).
I want to specify a default slice which is a known safe (or failsafe), but also want to allow the user to override it and specify a whole bunch of elements.
But if I do something like this:
Then what I get instead is that when I specify a command line option for that parameter - i.e.
--management-socket tcp://0.0.0.0:8080
then that just gets appended to the default slice, rather then replacing it.The text was updated successfully, but these errors were encountered: