thoom/gulp

Go-based HTTP REST client

gulp's Issues

Change contact email to thoom.net

Slowly moving away from thoomtech.com email domain to thoom.net

YAML conversion broken

Broke ability to pass YAML as JSON in 0.9.

Add binary releases

Set up a build environment that allows adding the release binaries for various formats. This should probably be done once I have added some testing.

Upgrade notice

Perhaps in the -version flag, add a notice if there is an upgrade available.

Update to Go 1.21

Trying to stay up to date on Go version number

socket: too many open files

Getting error socket: too many open files when trying to run too many --repeat-times. On macOS this happens around 252 repeats. It happens regardless of the number of concurrent connections.

Windows binary

Add building the windows binary to the output.

Add load testing delay

Create a randomized load testing delay to prevent pulses during testing.

This could have some configuration, including disabling completely in case you want to try to create pulses.

Update User-Agent String

Currently the user agent is thoom.Gulp/version-os-architecture, however, maybe it should be thoom.Gulp/version (OS; architecture)?

So instead of thoom.Gulp/1.0-darwin-amd64 it'd be thoom.Gulp/1.0 (darwin; amd64)

Add -url flag

By default, the API has the format gulp [flags/options] url. There are times when it would be useful to have the URL as part of the flag array instead of being required at the end.

Missing tests

The project is missing unit tests and travis CI integration.

Have the User-Agent include the build OS

Since we're building the version, may as well look at adding the OS as part of the User-Agent string.

`-ro`, `-so`, and `-I` uniqueness

The 3 display-related flags should be related to each other. Currently they can all be set and then behave weirdly.

Maybe just allow a single one and have an error if more than one are set? Or only use the last one?

Missing Content-Length when using put

When passing in a put, the content-length is missing

Move to go 1.13

Move from Go 1.11 to 1.13 and support for modules.

Colorized output

When using verbose display, color code success and error responses.

Upgrade to go 1.18

At a minimum, just rebuild in 1.18. Look at additional changes in 1.18 that may make sense to incorporate.

verbose timer

Add how long the response took in verbose display.

Obfuscate user defined PII headers

Sometimes there is PII/secret data passed in a header (like an API key). If I want to copy and paste the output to someone else, I currently have to copy it into something like VS Code, remove or obfuscate the secret manually, then copy the edited data.

It'd be cool if I could define certain headers in a config file to be secret/PII/secure and have the output automatically clean the header (ie. convert X-Secret-Header: abc123456def to X-Secret-Header: abc1xxxx6def)

TLS verification toggle

Right now, the client ignores TLS certificate errors. This should be toggle able at least in the config.

Allow payload to be dynamically generated using Go templates

It could be cool to pass a Go template file that could be used to dynamically create payload data. Maybe even support the ability to pass in a cli variable that could be used in the template.

Allow Gzip encoding

Dockerize this sucker

Provide a docker image that can be used if people don't want go installed on the system.

GHA Release is deprecated

Move to https://github.com/softprops/action-gh-release

Set default user-agent

While the user-agent can be overridden easily in the config, set a default (i.e. thoom/gulp or something).

block color output issues

Found some terminals that were displaying a color block weirdly.

Update to 1.17

Update to latest version of Go - currently 1.17

Docker image doesn't include OS in version

Should we use docker or alpine?

better verbose request output

Make the info provide in the verbose mode for the request better.

docker + /etc/hosts problems

The app doesn't pick up any /etc/hosts entries added via --add-host=DOMAIN:IP entries or with docker-compose.

Looks like this is related to this moby issue. Keep track to see if there are implementation options to handle it.

Can't use --add-host in Docker

Docker version of Gulp doesn't work with --add-host

Code Smell From SC

https://sonarcloud.io/project/issues?open=AYa5Mcy46tQoRdRwsvwU&id=gulp

Add -insecure flag

Rather than use -k, create an -insecure flag. This will be more intuitive.

Allow custom timeouts

Currently the client has a 300 second timeout. It should allow this to be customized per request as well as have a configuration value.

Support for Basic Auth

Add support for Basic authentication:

• -username, -password Cli flags
• config file basic_auth object

Add go language version to version dialog

👆

Add some curl shortcuts

-I should be like -m HEAD
-v should be like -verbose
-i could also be like -verbose

client-cert auth

Add the ability to pass in a client cert for handling client-cert based authorization

option to disable following redirects

The client will currently follow 301/302 responses. There should be a configuration and command line option to disable the feature.

disable color output if terminal doesn't support it

Some terminals don't handle the output properly. Investigate if there is a way for the client to determine whether or not to use a colored output.

Verbose setting only shows GULP-added Headers

The verbose display setting only shows headers that were added by GULP explicitly. It does not include additional headers that may be set by the HTTP client.

Support Apple Silicon

Currently only support Intel Macs.

Pipeline improvements

Add support for go vet and staticcheck as part of the pipeline to increase quality

Allow non-JSON post data

The client assumes that all post data is JSON, so if it's not JSON/YAML then the post data will cause an error.

Set default accept header

Create a default accept header. Probably something like application/json;q=1.0, */*;q=0.8

Add support for form data.

There should be a simple way to build form data.

For multipart/form-data, look at this example: https://stackoverflow.com/questions/20205796/golang-post-data-using-the-content-type-multipart-form-data#20397167

Add code coverage report

Add code coverage report using something like goveralls.