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.
When a user is required to use the --no-check-certificate option, they must include it for all subcommands. This makes the workflow a bit clunky for that use case.
Describe the solution you'd like
Have the --no-check-certificate option as a configuration parameter option stored in the settings.yaml file. When set, this would run all commands with that option set. This will allow the user to omit that option from the command line. NOTE: We should clearly warn the user that they are running in this mode for each request. Maybe a red warning text after each request?
Describe alternatives you've considered
The current command option works, but is not as clean.
Additional context
This is impacting customers with SSL decryption and other MITM solutions.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When a user is required to use the
--no-check-certificate
option, they must include it for all subcommands. This makes the workflow a bit clunky for that use case.Describe the solution you'd like
Have the
--no-check-certificate
option as a configuration parameter option stored in thesettings.yaml
file. When set, this would run all commands with that option set. This will allow the user to omit that option from the command line. NOTE: We should clearly warn the user that they are running in this mode for each request. Maybe a red warning text after each request?Describe alternatives you've considered
The current command option works, but is not as clean.
Additional context
This is impacting customers with SSL decryption and other MITM solutions.
The text was updated successfully, but these errors were encountered: