gruntwork-installer icon indicating copy to clipboard operation
gruntwork-installer copied to clipboard

A script to make it easy to install Gruntwork Modules

Results 13 gruntwork-installer issues
Sort by recently updated
recently updated
newest added

A user provided this error log to illustrate that they couldn't use the installer to install openvpn-admin on a VM. ``` gruntwork-install --binary-name openvpn-admin --repo https://github.com/gruntwork-io/terraform-aws-openvpn --tag v0.5.4 ``` Error:...

question

Trying to work out if this is a valid use case for something we are working on. We might take a different approach. TBC

This PR does the initial plumbing in bash for enabling download retries in the installer scripts. The general philosophy is to rely on the native capabilities of curl (and whatever...

#### [This issue is not valid - gruntworks modules are published via GitHub releases, not packages. ](https://github.com/gruntwork-io/gruntwork-installer/issues/73#issuecomment-1109705655) --- Hello 👋 My name is Peter and I work at FreeAgent. We...

enhancement

When calling `gruntwork-install` in a Dockerfile and attempting to download a private repo, we currently echo this INFO level log line to STDOUT: `2020-10-06 23:48:56 [INFO] [gruntwork-install] Repository is not...

bug

`bootstrap-gruntwork-installer.sh` installs `fetch` into `/usr/local/bin`. Depending on the OS and the user (e.g., root), this directory is not always on the `PATH`. As a result, the call to `fetch` in...

bug

A customer recently had an issue with curl failing to download `fetch`. The error is: ``` Step 10/24 : RUN curl -Ls https://raw.githubusercontent.com/gruntwork-io/gruntwork-installer/master/bootstrap-gruntwork-installer.sh | bash /dev/stdin --version v0.0.23 ---> Running...

bug

Every now and then GitHub API fails with GitHub API error `Failed to download file at the url https://api.github.com/repos/xxx/xxx/zipball/xxx. Received HTTP Response 502.`. To make the installer more resilient to...

enhancement

https://github.com/gruntwork-io/gruntwork-installer/blob/fe01f1098c0be99e876511e30e98c81ba3b4f596/bootstrap-gruntwork-installer.sh#L22 This is legacy code that never got used. That said, we should standardize on a common install location for all Gruntwork utilities. Perhaps `/opt/gruntwork//`?

bug

As I understand, to upgrade a tool we need to re-run the same command than for the installation, replacing the version. It will be good for the sake of simplicity...