Skip to main content
Self-service is a Git repository, not a web portal. In the DevHub track, the repository is named gc-devhub-{installation}-self-service. The desired state of your installation lives in the self-service.tfvars file at the root of the repository. When you merge a change to main, Terraform applies it. Backbase creates your GitHub organization and self-service repository when your installation is set up. For more information about the managed and DevHub tracks, see GitHub organization and repository structure.

​
What you manage

Through self-service.tfvars, you manage the following:
  • Users and seats: who can use your GitHub organization and installation, through the team_members section.
  • GitHub teams: membership of the self-service, applications-live, development, and development-admin teams.
  • Banking OS roles per runtime: Azure access for each runtime, such as Azure API Management and the AKS cluster.
  • Datadog and Grafana roles: access to logs, dashboards, monitors, and alerts.
  • Repositories from templates: API, connector, and SDK repositories created from Backbase templates.
  • Reviewers and pull request title rules: who reviews pull requests to applications-live, and which title scopes they need.
  • Secrets and infrastructure: GitHub secrets and additional infrastructure for your installation.

​
How changes work

To change your installation, follow these steps:
  1. Create a branch in the self-service repository.
  2. Edit self-service.tfvars to describe the state you want.
  3. Open a pull request to main.
  4. Wait for the Terraform plan comment on the pull request, and review the planned changes.
  5. Merge the pull request. Terraform applies the changes.
If you push more commits to the pull request, the Terraform plan runs again.