peimanja / amtoolcm-github-actions

GitHub Action for checking Prometheus Alertmanager configs

AMToolCM GitHub Actions

AMTool GitHub Actions allow you to check Prometheus Alertmanager config within GitHub Actions.

The output of the actions can be viewed from the Actions tab in the main repository view. If the actions are executed on a pull request event, a comment may be posted on the pull request.

Success Criteria

An exit code of 0 is considered a successful execution.

Usage

amomtool GitHub Actions are a single GitHub Action that executes amtool check-config subcommand.

name: Check Prometheus Alertmanager Config

on:
  pull_request:
    paths:
    - 'alertmanager/config.yml'

jobs:
  on-pull-request:
    name: On Pull Request
    runs-on: ubuntu-latest
    steps:
    - name: Checkout Repo
      uses: actions/checkout@master

    - name: Check Prometheus Alertmanager Config
      uses: peimanja/amtoolcm-github-actions@main
      with:
        amtool_actions_config: 'alertmanager/config.yml'
        amtool_actions_version: '0.21.0'
        amtool_actions_comment: true
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Inputs

Inputs configure amtool GitHub Actions to perform different actions.

• amtool_actions_config - (Required) Path to Alertmanager config file.
• amtool_actions_version - (Optional) amtool version to install and execute (Alertmanager bundle version). The default is set to latest and the latest stable version will be pulled down automatically.
• amtool_actions_comment - (Optional) Whether or not to comment on GitHub pull requests. Defaults to true.

Secrets

Secrets are similar to inputs except that they are encrypted and only used by GitHub Actions. It's a convenient way to keep sensitive data out of the GitHub Actions workflow YAML file.

• GITHUB_TOKEN - (Optional) The GitHub API token used to post comments to pull requests. Not required if the amtool_actions_comment input is set to false.

amtoolcm-github-actions's Issues

Need tag 0.0.2 on efe8ed780c4db35b958519129b3183d7cdaf120b

efe8ed7 merged a fix for unauthenticated git calls over git://
No tag was created for version 0.0.2 on this merge so the action with the fix can't be used yet

Validation Error: unknown time zone. Add `tzdata` pkg to Dockerfile

When running this action against alertmanager configs that contain time_intervals, and the location is set, the validation will fail as the timezone is not known.

The alpine:3 docker image does not contain tzdata, so the Dockerfile should add this package alongside the others.

# Without tzdata package
> amtool check-config alertmanager.yaml
Checking 'alertmanager.yaml'  FAILED: unknown time zone America/New_York

amtool: error: failed to validate 1 file(s)

# Add tzdata package
> apk add tzdata
(1/1) Installing tzdata (2023c-r1)
OK: 46 MiB in 28 packages
> amtool check-config alertmanager.yaml
Checking 'alertmanager.yaml'  SUCCESS
Found:
 - global config
 - route
 - 1 inhibit rules
 - 71 receivers
 - 1 templates
  SUCCESS