Skip to content
Branch: master
Find file History
bryankaraffa GitHub Policy Templates (#219)
* initial commit for github available seats policy


* Fixed typo

* Added README link to short_description

* Added version to long_description

* Added footer to email with information on project policy is running in

* Added Available Seats link to root README

* Renamed datasource declarations

* Changing category to Compliance

* Changing category to Compliance

* Initial commit of Compliance Policies

* Fixed URL to policy in description

* Added Empty Repository Policy

* Adding GitHub pagination

* Changing Policy Cred Name

* Removing limit after adding pagination

* Added support for github pagination

* Adding Empty Repository

* Fixed typo in description

* Updated README - removed permission thats not required

* Renaming Policies and improving descriptions

* Removed typo
Latest commit 67dd7f2 May 13, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information. GitHub Policy Templates (#219) May 13, 2019 GitHub Policy Templates (#219) May 13, 2019 GitHub Policy Templates (#219) May 13, 2019 Available Seats

What it does

This Policy Template will get the total used/available seats for a Organization and create an incident if the number of available seats fall outside the policy's min and max parameters.


  1. Organizations to check - Example: flexera
  2. Allowed Minimum Available Seats - Example: 10
  3. Allowed Maximum Available Seats - Example: 50
  4. Email address to send escalation emails to - Example:

Policy Actions

The following policy actions are taken on any resources found to be out of compliance.

  • Send an email report

Required Permissions

This policy requires permissions to access API as the Owner of the Organization(s). Before applying this policy, create a Personal Access Token under the user with Owner role -- adding the admin:org read:org scopes at minimum, and save the token in the project on Cloud Management as credential named GITHUB_ORG_ADMIN_ACCESS_TOKEN. If you are using other Governance Policies for, you may need to include additional roles to sate the need of all policies which use the same credential. Optionally, you can generate a token with full permission and avoid any issues.

This policy requires permissions to access RightScale resources (credentials). Before applying this policy add the following roles to the user applying the policy. For more information on modifying roles visit the Governance Docs

  • Cloud Management - credential_viewer or admin
  • Cloud Management - observer


This Policy Template does not launch any instances, and so does not incur any cloud costs.

You can’t perform that action at this time.