Exploring the Changes Done By the Boot
In this lesson, we will take a look at all the files that were changed because of Jenkins X Boot.
Now, let’s take a look at the changes Jenkins X Boot did to the local copy of the repository.
jx repo --batch-mode
Please click the commits tab and open the last one. You’ll see a long list of the files that changed.
That’s a long list, isn’t it? Jenkins X Boot changed a few files. Some of those changes are based on our answers, while others are specific to the Kubernetes cluster and the vendor we’re using.
We won’t comment on all the changes that were done, but rather on the important ones, especially those that we might choose to modify in the future.
The env/parameters.yaml file
If you take a closer look at the output, you’ll see that it created the env/parameters.yaml file. Let’s take a closer look at it.
cat env/parameters.yaml
The output, in my case, is as follows.
adminUser:password: vault:jx-boot/adminUser:passwordusername: adminenableDocker: falsepipelineUser:email: viktor@farcic.comtoken: vault:jx-boot/pipelineUser:tokenusername: vfarcicprow:hmacToken: vault:jx-boot/prow:hmacToken
The parameters.yaml file contains the data required for Jenkins X to operate correctly. There are the administrative username and password and the information that Docker is not enabled (enableDocker). The latter is not really Docker but rather that the system is not using an internal Docker Registry but rather an external service. Further on, we can see the email, the token, and the username ...