v1.32.1 Breaking change: use PACKAGES_INSTALL_PATH instead of INSTALL_PATH

Our apologies for introducing a breaking change in a patch release. We did not realize it was a breaking change when we made it.

With this version, build-harness is no longer influenced by the setting of the INSTALL_PATH environment variable. We made this change because INSTALL_PATH is generic and used by other projects for other purposes. Instead, build-harness now uses the new environment variable PACKAGES_INSTALL_PATH to determine where to install any tools it automatically installs.

If you were using something like:

INSTALL_PATH=${GITHUB_WORKSPACE:-/usr/local}/bin make packages/install/terraform-docs

to install a command (terraform-docs in this example), all you need to do is replace INSTALL_PATH with PACKAGES_INSTALL_PATH

🐛 Bug Fixes

Disambiguate packages install path from other uses of INSTALL_PATH @Nuru (#377)

what

• Use PACKAGES_INSTALL_PATH instead of INSTALL_PATH to determine where build-harness installs its tools

why

• Other Makefiles use INSTALL_PATH to determine where to install their build artifacts (typically /usr/local/bin) but that does not mean build-harness should be installing its tools there