https://github.com/mcrmonkey/hashi-pkg
Package hashicorp tools
https://github.com/mcrmonkey/hashi-pkg
docker-image hashicorp packages
Last synced: 23 days ago
JSON representation
Package hashicorp tools
- Host: GitHub
- URL: https://github.com/mcrmonkey/hashi-pkg
- Owner: mcrmonkey
- Created: 2018-06-01T18:31:38.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2023-04-28T22:58:21.000Z (about 3 years ago)
- Last Synced: 2025-07-05T04:17:24.684Z (11 months ago)
- Topics: docker-image, hashicorp, packages
- Language: Shell
- Homepage:
- Size: 4.88 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Hashi-pkg
Downloads a hashicorp tool and creates packages for installation via yum or apt
**Please note**: This tool is _not_ created, supported and/or endorsed by Hashicorp. Use at your own risk etc.
### Why
Hashicorp distribute their tools in .zip files which need extracting and
putting in to the correct place to run.
This can be a bit of faf when updates are released and existing systems need
to be updated.
Plugging the tools in to a users package manager can help keep things up to
date and ensure an consistent installation environment.
## How
For ease all operations are triggered via a `Makefile`
To avoid adding extra junk to your system this makes use of a docker container with packaging tools installed in to it.
To build the image run the following on your system:
```shell
make container
```
To get the latest terraform and turn it in to a package run the following:
```shell
make package
```
To get an older version of terraform specify the version, like so:
```shell
make VERSION="0.7.4" package
```
To specify an alternate tool specify the tool name, like so:
```shell
make TOOL="packer" package
```
The `TOOL` and `VERSION` can be specified together to get specific versions of tools.
If these variables are not specified it will default to getting and packaging the latest version of terraform.
## Todo
There are some things to be aware of:
* Due to the format of the changelog being different to what the RPM builder
tool expects the change log is not included in the RPM package.
* The Docker image is probably a little larger than it should be due to the
repo building tools that are included but aren't currently used