CodeStation is the secure and tamper-proof artifact repository ensures that deployed components are identical to the components that were tested in preproduction environments. Without the repository, artifacts must be pulled from network shares or some other system, increasing both security risks and the potential for error.
We create a component and select “Source Configuration Type” which has many options such as FileSystem, Git, Maven etc. These are source of Artifacts represent deployable items such as files, images, databases, configuration materials, or anything else that is associated with a software project. During the deployment of “Application Process” of Component, its gets copied to CodeStation of the option is checked in Component.
Thus, CodeStation is a relatively secure storage with integrity checks via checksums etc. The Artifact stored in CodeStation can not be interact with it directly but can be used during deployement as this is Checksums. If you want to modify a file in one of your components’ versions, you need to use an agent to deploy it somewhere, run whatever you do to modify it and then upload or import it into CodeStation.
The checksums artifacts in Codestationn are getting stored in the pat /opt/ibm-ucd/server/appdata/var/repository/blob with names of the files and folders encrypted ( as 50542faa-e510-44c1-8ae4-f7d6f157ccb4 )
- Understanding Kubernetes’s Taints and Tolerations in easy way - July 5, 2020
- Understanding Node Selector and Node Affinity in Kubernetes - July 5, 2020
- Terrafrom – Example Code for remote-exec provisioner - July 5, 2020