github_organization_settings resource and data object return plan as attribute

[jeremiahbowen]

I wrote the following code to get this myself but I would prefer to have this returned natively by the resource/data github_organization_settings objects. This particular snippet is an early warning that we need to add seats in github before we apply to add members to the organization.

#!/bin/env bash

set -e

data="$(curl -s -L -H "Authorization: Bearer $GITHUB_TOKEN" "https://api.github.com/orgs/pagerinc")"
printf "%s" "$data" | jq -c "{seats: .plan.seats|tostring,filled_seats: .plan.filled_seats|tostring}"
# scripts/check_seats

locals {
  # github_users is managed externally but I'm including a mock structure for reference
  github_users        = {
    test1: "admin",
    test2: "member",
  }
}

resource "null_resource" "check_seats" {
  triggers = {
    hold-value = data.external.check_seats.result.seats >= length(keys(local.github_users)) ? "seats good" : "Add github seats before apply. Needed: ${length(local.configured_seats)}"
  }
  lifecycle {
    prevent_destroy = true
  }
}

data "external" "check_seats" {
  program = ["bash", "${path.module}/scripts/check_seats"]
}

Basically, if the null_resource is applied when "seats good", it will fail when we have to add seats in a terraform plan. I would prefer to retrieve the plan details within the official objects.

[warrickhill]

+1

It would be really good if we could mange the number of seats too.