Use Cases for Adding Web Artifacts and Other Siebel Artifact Files

This topic provides detailed information about the steps to support use cases for adding or updating web artifacts or other Siebel artifact files after deployment or as part of incremental changes. No restarts apply in these use cases. This topic is part of Use Cases for Making Incremental Changes.

Now all the Siebel artifact files will be part to <namespace>-helmcharts git project and it is propagated to siebel applications from here.

One can view and edit Siebel artifacts file from the location <namespace>-helmcharts/siebel-artifacts/build/mde.

To add a new siebel artifacts files after deployment:

Exec into the SCM container:
```
 docker exec -it cloudmanager bash
```

Execute the following command:

cd /home/opc/siebel/<ENV_ID>/<namespace>-helmcharts/siebel-artifacts/build/mde

Add new Siebel artifact files in the required path locations. If the required path does not exist, then you can create the folder path and include new files.
Upgrade the siebel-artifacts helmcharts version, as follows:
```
vi /home/opc/siebel/<ENV_ID>/<namespace>-helmcharts/siebel-artifacts/Chart.yaml
```
Increment the version and save.
Push all changes to the remote GitLab repository, as follows:
```
git pull
git status
git add <file1> <file2> 
git commit -m "<message>"
git push
```
You can also perform the above steps from the GitLab user interface.

Once the changes are pushed, flux controllers identify the change in the siebel-artifacts helmcharts version and start an upgrade. As part of the upgrade, a preupgrade job, image-builder, is triggered. The image-builder job builds a custom container image with a new tag having all the updated artifact files.
- If there is no difference, then the image-builder job exits with an appropriate message.
- If there are changes from the previous build, then the image-builder job builds a custom container image with a new tag and pushes it to the container registry.
Later, the new container image tag is identified and updated in the required Git references by the flux controllers. Then the siebserver, sai, and gateway pods are restarted and deployed with the new container image having updated Siebel artifact files.
Once the pods are restarted, to realize the changes, access one of the containers using the following command and verify if new files are present:

kubectl exec -it <pod_name> bash -n <namespace>
Verify the files in the files, images, and scripts directories from your browser:
```
https://<EXTERNAL_IP>/siebel/files/custom/<file>
https://<EXTERNAL_IP>/siebel/images/custom/<file>
https://<EXTERNAL_IP>/siebel/scripts/siebel/custom/<file>
```
Note: You will find an inline comment # {"$imagepolicy": <namespace>:cm-siebel-image-policy:tag"} next to some image tags in the Git repository. This is a marker used for automation; do not modify this comment. To enable custom web artifacts in applications, you must update manifest entries manually.