🖥
Infrastructure as Code
Learn how to connect your preferred Infrastructure as Code (IaC) source for autonomous configuring syncing by Sedai.
To add an IaC integration, navigate to Settings -> Integrations and click Add Integration, then Infrastructure as Code (IaC) Source. You can add multiple IaC integrations.
You must enable sync for each IaC integration you wish to use from the Settings -> IaC page.
The following details are required to connect GitHub as an IaC source:
- Profile name
- Workspace name
- Repository name
- Default branch
- Token: Sedai uses Bitbucket Repository Access Tokens to read IaC template files and create merge requests. Visit Atlassian Docs to learn more.
- Configuration template: Choose your preferred configuration template:
- 1.System: Sedai will provide code changes in a standard YAML format for you to examine and make any desired changes to your own IaC template.
- 2.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.
- Self-Hosted Endpoint: If you are self-hosting Bitbucket, enter your endpoint.
- File Format: Sedai offers three options for creating merge requests:
- 1.Single request: Creates a single merge request containing configurations for all resources, including those that did not have a change
- 2.Single file with configuration changes: Creates a single merge request containing all resource configuration changes from a specified time interval
- 3.Multiple requests: Creates separate requests for each resource with configuration changes
You can also choose whether you want file updates for all resources or select groups of resources.
Once you've entered the required details, click the Test Connection button to verify your connection works. If the connection fails, please double-check that you've entered the correct information in each field. If the connection is successful, click Save.
The following details are required to connect GitHub as an IaC source:
- Profile name
- GitHub username
- Repository name
- Default branch
- 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. Visit GitHub Docs to learn more.
- Configuration template: Choose your preferred configuration template:
- 1.System: Sedai will provide code changes in a standard YAML format for you to examine and make any desired changes to your own IaC template.
- 2.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.
- Self-Hosted Endpoint: If you are self-hosting GitHub, enter your endpoint.
- File Format: Sedai offers three options for creating merge requests:
- 1.Single file with configuration changes: Uses a single file to hold all the resource configurations that have changed within a specific time interval
- 2.Single file summary: Uses a single file to store all resource configurations, including those that did not have a change
- 3.Multiple files: Creates separate file for each resource with configuration changes
- Target file location: Add the target path for the files Sedai will add.
You can also choose whether you want file updates for all resources or select groups of resources.
Once you've entered the required details, click the Test Connection button to verify your connection works. If the connection fails, please double-check that you've entered the correct information in each field. If the connection is successful, click Save.
The following details are required to connect GitLab as an IaC source:
- GitLab profile name
- 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. Visit GitLab Docs to learn more.
- Configuration template: Choose your preferred configuration template:
- 1.System: Sedai will provide code changes in a standard YAML format for you to examine and make any desired changes to your own IaC template.
- 2.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.
- Self-Hosted Endpoint: If you are self-hosting GitLab, enter your endpoint.
- File Format: Sedai offers three options for creating merge requests:
- 1.Single request: Creates a single merge request containing configurations for all resources, including those that did not have a change
- 2.Single file with configuration changes: Creates a single merge request containing all resource configuration changes from a specified time interval
- 3.Multiple requests: Creates separate requests for each resource with configuration changes
You can also choose whether you want file updates for all resources or select groups of resources.
Once you've entered the required details, click the Test Connection button to verify your connection works. If the connection fails, please double-check that you've entered the correct information in each field. If the connection is successful, click Save.
Last modified 6d ago