Git Repositories for Siebel CRM Deployment

GitOps is a paradigm that uses Git to declaratively automate deployments, and improves operational efficiency by managing infrastructure and application code.

SCM uses Git repositories to store the configuration of each deployment that it performs. In case of lift and shift, Git repositories store the artifacts sourced from the source environment using the Siebel Lift utility, and then the configuration files are accessed from the Git repositories to perform the actual deployment. Git repositories also store the configuration artifacts for the greenfield use case, including the one described in Customizing Configurations Prior to Greenfield Deployment.

Each Siebel CRM deployment requires the following two Git repositories:

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

SCM can either:

• Use existing repositories: If you've existing Git repositories hosted on any standards-compliant Git distribution, such as OCI DevOps, 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.

  Optionally, you can also create Git repositories on any standards-compliant Git distribution, such as OCI DevOps, GitHub, GitLab, Bitbucket, and so on before using them to provision Siebel CRM through SCM. For example, you can create Git repositories in OCI DevOps as follows:

  1. Log in to OCI Console.
  2. Create an OCI DevOps project. For detailed steps to create an OCI DevOps project, refer Creating a Project.
  3. Create repositories under the OCI DevOps project. For detailed steps to create repositories, refer Creating a Repository.
• Create repositories: If you want SCM to create Helm chart and SCM repositories as part of Siebel CRM provisioning, you must install GitLab Community Edition (CE) and configure the Siebel CRM deployment payload to use GitLab as the Git repository, as follows:
  1. Download, install, and configure GitLab CE as follows:
     1. Enable and start the OpenSSH server daemon.
     2. Add the GitLab package repository.
     3. Install GitLab CE.
     4. Configure GitLab CE.

     For detailed steps to install GitLab CE, refer Install the Linux package on AlmaLinux and RHEL-compatible distributions.

  2. Configure HTTPS for secure communication. For steps to configure HTTPS, refer the "Configure HTTPS manually" section under Configure SSL for a Linux package installation.
  3. Set the git_type parameter to gitlab.
  4. 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.