Amtool (#271)

* update: addition of amtool

* update: addition of amtool

* update: amtool build fixes

* update: amtool build fixes

* update: amtool apk build

* fix: add amtool to auto-label

* fix: Makefile fix?

* fix: Makefile auto-label

* update: readme update

* update: auto-label space update

.github/auto-label.yml

@@ -16,6 +16,7 @@ scripts:
 - bin/**
 - tasks/**
 vendor: vendor/**
+vendor/amtool: vendor/amtool/**
 vendor/assume-role: vendor/assume-role/**
 vendor/atlantis: vendor/atlantis/**
 vendor/awless: vendor/awless/**

README.md

@@ -227,15 +227,29 @@ packages/uninstall/%:
 ### Contributing Additional Packages
 In addition to following the Contributing section, the following steps can be used to add new packages for review (via a PR).
 1. Clone an existing, similar, package within the vendors directory. Name the new folder with the same name as the binary package being installed.
-2. At a minimum, update the `VERSION`, `DESCRIPTION`, and `Makefile` to reflect the binary being installed. Ensure that a test section exists and works.
+2. At a minimum, update the `VERSION`, `DESCRIPTION`, and `Makefile` to reflect the binary being installed. Ensure that a test task exist in the package Makefile.
 3. Test the install and ensure that it downloads and runs as expected (`make -C install <your_package> INSTALL_PATH=/tmp`)
-4. Test the build (`make all`)
-5. Update the `README.md` (`make readme/build`)
+4. Test the apk build (see below)
+5. Update the `README.md` (`make init readme/deps readme`)
+
+### Testing apk builds
+
+To validate that a new package will build into an apk you can use the following steps;
+
+```bash
+make docker/build/apk/shell
+make -C vendor/<appname> apk
+# Some temp build files in the volume mount set user/group to nobody/nobody for apk building.
+# It is easier to remove them while within the docker container.
+rm -rf ./tmp/build.*
+exit
+```
 
 
 
 ## Makefile Targets
 ```
+amtool                    0.19.0     Tool for interacting with the Alertmanager API
 assume-role               0.3.2      Easily assume AWS roles in your terminal.
 atlantis                  0.10.2     Terraform For Teams
 awless                    0.1.11     A Mighty CLI for AWS

README.yaml

@@ -181,11 +181,24 @@ examples: |-
   ### Contributing Additional Packages
   In addition to following the Contributing section, the following steps can be used to add new packages for review (via a PR).
   1. Clone an existing, similar, package within the vendors directory. Name the new folder with the same name as the binary package being installed.
-  2. At a minimum, update the `VERSION`, `DESCRIPTION`, and `Makefile` to reflect the binary being installed. Ensure that a test section exists and works.
+  2. At a minimum, update the `VERSION`, `DESCRIPTION`, and `Makefile` to reflect the binary being installed. Ensure that a test task exist in the package Makefile.
   3. Test the install and ensure that it downloads and runs as expected (`make -C install <your_package> INSTALL_PATH=/tmp`)
-  4. Test the build (`make all`)
-  5. Update the `README.md` (`make readme/build`)
+  4. Test the apk build (see below)
+  5. Update the `README.md` (`make init readme/deps readme`)
 
+  ### Testing apk builds
+  
+  To validate that a new package will build into an apk you can use the following steps;
+
+  ```bash
+  make docker/build/apk/shell
+  make -C vendor/<appname> apk
+  # Some temp build files in the volume mount set user/group to nobody/nobody for apk building.
+  # It is easier to remove them while within the docker container.
+  rm -rf ./tmp/build.*
+  exit
+  ```
+  
 # Contributors to this project
 contributors:
   - name: "Erik Osterman"

docs/targets.md

@@ -1,5 +1,6 @@
 ## Makefile Targets
 ```
+amtool                    0.19.0     Tool for interacting with the Alertmanager API
 assume-role               0.3.2      Easily assume AWS roles in your terminal.
 atlantis                  0.10.2     Terraform For Teams
 awless                    0.1.11     A Mighty CLI for AWS

vendor/amtool/DESCRIPTION

@@ -0,0 +1 @@
+Tool for interacting with the Alertmanager API

vendor/amtool/LICENSE

@@ -0,0 +1 @@
+Apache 2.0

vendor/amtool/Makefile

@@ -0,0 +1,17 @@
+export VENDOR ?= prometheus
+export APK_BUILD_TEMPLATE ?= APKBUILD.github-binary
+#export APKBUILD_DEPENDS += libc6-compat musl
+export PACKAGE_REPO_NAME = alertmanager
+export DOWNLOAD_URL ?= $(PACKAGE_REPO_URL)/releases/download/v$(PACKAGE_VERSION)/alertmanager-$(PACKAGE_VERSION).$(OS)-$(ARCH).tar.gz
+
+include ../../tasks/Makefile.package
+include ../../tasks/Makefile.apk
+
+install:
+	$(call download_tarball)
+
+test:
+	$(PACKAGE_EXE) --version
+
+package/prepare::
+	mv src/alertmanager-$(PACKAGE_VERSION).$(OS)-$(ARCH)/$(PACKAGE_EXE) src

vendor/amtool/RELEASE

@@ -0,0 +1 @@
+0

vendor/amtool/VERSION

@@ -0,0 +1 @@
+0.19.0