Git Repositories for Siebel CRM Deployment

GitOps is a deployment model that uses Git to automate deployments, enhances security, and improves operational efficiency by managing infrastructure and application code. Each Siebel CRM deployment requires the following two Git repositories:

• SCM repository to store SCM templates and release YAMLs.
• Helm chart respository to store Helm charts. It also holds the details of the charts installed and upgrades.

SCM can either:

• Create repositories: If you want SCM to create Helm chart and SCM repositories as part of Siebel CRM provisioning, you must install GitLab and configure the Siebel CRM deployment payload to use GitLab as the Git repository, as follows:
  1. Set the git_type parameter to gitlab.
  2. Configure the gitlab section. For details of the parameters to include in the gitlab section, see Parameters in Payload Content.

     You must ensure that GitLab is accessible through HTTP/HTTPS for API access to create or delete repositories.

     For an example payload, see the payloads in the Example Payload to Deploy Siebel CRM topic.

• Use existing repositories: If you've existing Git repositories hosted on any standards-compliant Git distribution, such as Oracle DevOps Service, GitHub, GitLab, Bitbucket, and so on, you can use it to provision Siebel CRM through SCM. To use existing Git repositories, in the Siebel CRM deployment payload:
  1. Set the git_type parameter to byo_git.
  2. Configure the byo_git section. For details of the parameters to include in the byo_git section, see Parameters in Payload Content.

     In this case, SCM will override the data in the Git repositories; that is, it will delete existing data in the repositories and then commit SCM data.

     For an example payload, see the payloads in the "Example Git Section for BYO-Git" section of the Example Payload to Deploy Siebel CRM topic.