Skip to content
Permalink
Branch: master
Commits on Feb 14, 2020
  1. Remove the code that (un)installed the gds-nagios-plugins package

    issyl0 committed Feb 14, 2020
    - Now that Puppet has run everywhere with the changes from 43e4afe -
      to uninstall the `gds-nagios-plugins` package - we can remove the
      `exec` that did that.
  2. Merge pull request #10145 from alphagov/rm-gds-nagios-plugins

    issyl0 committed Feb 14, 2020
    Remove the `gds-nagios-plugins` package
  3. Remove the `gds-nagios-plugins` package

    issyl0 committed Feb 14, 2020
    - We've moved everything that used to be here out of
      alphagov/nagios-plugins and into the plugins directory of this repo.
  4. Merge pull request #10144 from alphagov/move-check_puppetdb_ssh_host_…

    issyl0 committed Feb 14, 2020
    …keys_check
    
    Import `check_puppetdb_ssh_host_keys` from `alphagov/nagios-plugins`
  5. Import `check_puppetdb_ssh_host_keys` from `alphagov/nagios-plugins`

    issyl0 committed Feb 14, 2020
    - This was in the alphagov/nagios-plugins repo, which not very many
      people either have permissions to, or realise is still used. We're going
      to archive that repo.
Commits on Feb 13, 2020
  1. Merge pull request #10142 from alphagov/fix-check-scripts-some-more

    issyl0 committed Feb 13, 2020
    Fix check scripts' `nagios_*` methods to be useable
  2. Fix check scripts' `nagios_*` methods to be useable

    issyl0 committed Feb 13, 2020
    - In `alphagov/nagios-scripts`, the output functions were [extracted
      into their own module that was
      `import`ed](alphagov/nagios-plugins@1ec7bdc).
    - We need those functions in each script (we can refactor it later to be
      better?) for the outputs to work.
  3. Merge pull request #10140 from alphagov/import-check_apt_security_upd…

    issyl0 committed Feb 13, 2020
    …ates-from-nagios-plugins-repo
    
    Import `check_apt_security_updates` from `alphagov/nagios-plugins`
  4. Import `check_apt_security_updates` from `alphagov/nagios-plugins`

    issyl0 committed Feb 13, 2020
    - This was in the alphagov/nagios-plugins repo, which not very many
      people either have permissions to, or realise is still used. We're going
      to archive that repo.
  5. Merge pull request #10139 from alphagov/fix-check_reboot_required-fil…

    issyl0 committed Feb 13, 2020
    …epath
    
    Fix typo in path to check_reboot_required Nagios plugin script
  6. Merge pull request #10137 from alphagov/import-check_reboot_required-…

    issyl0 committed Feb 13, 2020
    …from-nagios-plugins-repo
    
    Import `check_reboot_required` script from alphagov/nagios-plugins
  7. Import `check_reboot_required` script from alphagov/nagios-plugins

    issyl0 committed Feb 13, 2020
    - This was in the alphagov/nagios-plugins repo, which not very many
      people either have permissions to, or realise is still used. We're
      going to archive that repo.
    - It seems better suited to live in here, with the other (very similarly
      named) `check_reboots_required` which uses it. :exploding_head:
Commits on Feb 11, 2020
  1. Merge pull request #10133 from alphagov/rm-terraboard

    issyl0 committed Feb 11, 2020
    Remove Terraboard fully
  2. Remove Terraboard fully

    issyl0 committed Feb 11, 2020
    - Now that #10130 is deployed in all AWS environments to `ensure =>
      absent` the resources.
  3. Merge pull request #10130 from alphagov/rm-terraboard

    issyl0 committed Feb 11, 2020
    Remove Terraboard from the infrastructure
Commits on Feb 7, 2020
  1. terraboard: `ensure => absent` everywhere

    issyl0 committed Feb 7, 2020
  2. Remove Terraboard from the infrastructure

    issyl0 committed Feb 7, 2020
    - Terraboard was [introduced in 2018](#8143) to help us track Terraform state between environments, to help with the AWS migration.
    
    - Since then, it hasn't got much use - mostly, we don't remember it exists. It hasn't helped with the goal of keeping environments in sync if any of the recent [Terraform deploy diffs](https://ci-deploy.integration.publishing.service.gov.uk/job/Deploy_Terraform_GOVUK_AWS/) are anything to go by.
    
    - It uses an old, unmaintained version of OAuth2 Proxy which we've had to build a [custom Docker image](https://github.com/alphagov/govuk-oauth2-proxy-docker/blob/master/Dockerfile) for. Both of these projects are now archived.
    
    - There's [documentation on the required engineering work](https://github.com/alphagov/govuk-developer-docs/blob/5ce8d7bd10cdceb7b89309ae388a41016dd2ab64/source/manual/use-terraboard-to-monitor-terraform-state.html.md#docker-image-for-oauth2-proxy) to get us up to date and stop maintaining so much custom code. This has recently (2020) increased because [GitHub are deprecating the authentication APIs that v2.2.0 uses](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/#authenticating-using-query-parameters) and will keep sending emails every three days until we stop using it.
    
    - Doing that engineering work will - we hypothesize - cost more than the value that Terraboard currently provides. So, delete Terraboard. To add some weight to this, a recent poll that I did in Slack had most respondents on the item "is a Terraboard an upside down Hoverboard", indicating that most devs had never heard of it.
    
    - Other considerations included: getting rid of OAuth2_Proxy because Terraboard is behind office IP restrictions on AWS. But: is Terraboard that valuable as a thing?
You can’t perform that action at this time.