Ask or search…
K
🖥

Infrastructure as Code (IaC)

Learn how to connect your preferred Infrastructure as Code (IaC) source to automatically sync configurations from Sedai.
Learn more about how Sedai works with CI/CD workflows.
To add an IaC integration, navigate to Settings -> IaC and click Add Integration. Sedai currently supports the following IaC sources. Select a provider to view specific details required to integrate.
You will additionally need to configure details about your template, file format, and whether PRs will be created for all resources or a subset of resources:
  • Configuration Template:
    • System (YAML format)
    • Use existing: Sedai will read and make changes to your IaC template. This option requires you to provide the HELM or Terraform CSV mapping so Sedai can locate the variable files and names.
  • Merge Request/File Format:
    • Single: Creates a single merge request/file containing configurations for all resources, including those that did not have a change
    • Multiple: Creates separate merge requests/files for each changed resource with its configuration changes
  • File Updates: You can set up your PRs to include configuration updates for all resources connected to Sedai, or for specific resources based on group(s). Learn more about setting up groups here.
Once you've entered the required details for your selected provider, click the Test Connection button to proceed. Make sure to enable Sedai to sync configuration changes and save the integration.

Bitbucket

The following details are required to connect Bitbucket:
Required
Description
Nickname
Create a unique identifier to reference within Sedai; this helps distinguish between multiple Bitbucket integrations.
Workspace ID
In Bitbucket, avigate to your profile and settings.
Repository Name
This can be found in the repository URL or from the Repository details within Bitbucket.
Default Branch
Optional
Token
Sedai uses Bitbucket Repository Access Tokens to read IaC template files and create merge requests. View Atlassian Docs to learn more.
Self-hosted Endpoint
Optional

GitHub

The following details are required to connect GitHub:
Required
Description
Nickname
Create a unique identifier to reference within Sedai; this helps distinguish between multiple GitHub integrations.
Username
This is used to access your repository via API; we recommend using the username of whoever creates the integration.
Repository Name
The repository you want Sedai to push PRs to.
Default Branch
Defaults to main; enter an alternate branch to customize.
Token
Sedai uses GitHub Personal Access Tokens to read IaC template files and create merge requests. The provided token should have access to all the projects passed in the CSV file. View GitHub Docs to learn more.
Self-hosted Endpoint
Optional
Target File Location
The path for files that Sedai will add

GitLab

The following details are required to connect GitLab:
Required
Description
Nickname
Create a unique identifier to reference within Sedai; this helps distinguish between multiple GitLab integrations.
Username
You can find this in your GitLab profile.
Project ID
This is used to validate the token and ensure Sedai can connect to your GitLab. The actual project ID can be set at the resource level, which can be provided in a CSV file.
Token
Sedai uses GitLab Personal Access Tokens to read IaC template files and create merge requests. The provided token should have access to all the projects passed in the CSV file. View GitLab Docs to learn more.
Self-hosted Endpoint
Optional
Last modified 14d ago