GitHub
Integrate GitHub with Cloudaware to ingest organizations, repositories, issues, pull requests, workflows, and related SDLC metadata for DevOps governance and reporting.
info
- Audience: Cloudaware administrators, DevOps
- Outcome: The GitHub account is connected, and GitHub objects are available in the CMDB for repository governance, workflow visibility, and application correlation
Capabilities
The integration supports:
- Read-only discovery of GitHub organizations, repositories, issues, pull requests, workflows, users, teams, and packages in the CMDB
- Relationships between repositories, SDLC activity, applications, and related cloud assets
- DevOps governance and SDLC posture reporting in Cloudaware
Prerequisites
Before you begin, make sure you have:
- Access to a Cloudaware account.
- A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
- GitHub personal access token (fine-grained or classic) with the required read scopes:
- For fine-grained access tokens:
- Actions
- Codespaces
- Contents
- Dependabot alerts
- Environments
- Issues
- Pull requests
- Secrets*
- Webhooks
- Workflows
- For tokens (classic):
repo(full access for private repositories) orpublic_repo(public repositories only)workflowread:packagesread:orgread:repo_hookadmin:org_hookcodespaceread:project
- For fine-grained access tokens:
note
*Cloudaware collects only metadata of secrets.
Add a GitHub Account to Cloudaware
To connect your GitHub account to Cloudaware:
- In Cloudaware, go to Admin.
- Find GitHub Accounts, then click + ADD.
- Enter the following values:
- Name: A display name for this connection.
- Token: The GitHub personal access token.
- Click SAVE.
- Confirm that the integration status indicator is green.
View GitHub Data in CMDB
To browse discovered GitHub resources:
- In Cloudaware, open CMDB Navigator.
- In the left pane, select GITHUB.
- Open an object list, e.g., GitHub Repositories or GitHub Issues, to view records.
Supported Objects
Cloudaware ingests the following GitHub objects:
| GitHub Object | CMDB Object API Name |
|---|---|
| GitHub Account | CA10GH__CaGithubAccount__c |
| GitHub Branch | CA10GH__CaGithubBranch__c |
| GitHub Codespace | CA10GH__CaGithubCodespace__c |
| GitHub Dependabot Alert | CA10GH__CaGithubDependabotAlert__c |
| GitHub Environment | CA10GH__CaGithubEnvironment__c |
| GitHub Issue | CA10GH__CaGithubIssue__c |
| GitHub Organization | CA10GH__CaGithubOrganization__c |
| GitHub Package | CA10GH__CaGithubPackage__c |
| GitHub Project | CA10GH__CaGithubProject__c |
| GitHub Pull Request | CA10GH__CaGithubPullRequest__c |
| GitHub Repository | CA10GH__CaGithubRepository__c |
| GitHub Secret (metadata) | CA10GH__CaGithubSecret__c |
| GitHub Team | CA10GH__CaGithubTeam__c |
| GitHub User | CA10GH__CaGithubUser__c |
| GitHub Webhook | CA10GH__CaGithubWebhook__c |
| GitHub Workflow | CA10GH__CaGithubWorkflow__c |
Troubleshooting
note
Initial data collection may take time to complete.
Authentication Fails or Integration Shows Red Status
- Verify that the GitHub token is active and copied correctly.
- Confirm that the token has read access to the organizations and repositories Cloudaware must discover.
- Check whether the token has expired or was revoked.
- Re-enter the token by editing the integration in Cloudaware.
Repositories or Organizations Are Missing
- Confirm that the token owner can access the missing organizations or repositories in GitHub.
- Review token scopes and organization access restrictions.
- In CMDB Navigator, verify that you are viewing the GITHUB section and related resources.
Still stuck? Contact Cloudaware Support at support@cloudaware.com with the integration name and a brief description of the issue.
Reconfigure or Remove the Integration
warning
To rotate credentials, edit the existing integration instead of deleting and re-creating it.
Update the Integration Details
- Go to Admin.
- Select GitHub Accounts.
- Select the specific integration.
- Open the three-dot menu (⋮), then click Edit.
- Update the required fields.
- Click Save.
Remove the Integration from Cloudaware
- Go to Admin.
- Select GitHub Accounts.
- Select the specific integration.
- Open the three-dot menu (⋮), then click Delete.
- Confirm the deletion if prompted.
Security Notes
- Use a dedicated GitHub token for Cloudaware discovery.
- Grant only the minimum read scopes required for the organizations, repositories, and metadata Cloudaware must discover.
- Prefer token expiration where supported and rotate tokens according to your organization's policy.
- Avoid using personal administrator tokens for long-running integrations.
- Update the Cloudaware integration immediately if the token is revoked, regenerated, or expires.