WEBVTT 00:05.910 --> 00:12.120 Looking back again at our configuration and at the command that we have executed, there's still a question 00:12.120 --> 00:19.170 regarding how exactly does Surján know to use the tokens and a username that we have provided as environment 00:19.170 --> 00:19.640 variables? 00:20.100 --> 00:26.070 Because if you look at the command, you would only see that we instructed the location of the project 00:26.670 --> 00:28.010 and the name of the domain. 00:28.560 --> 00:34.830 But after that, apparently Serj knew what to deploy, which is the account, and had to right permission 00:34.830 --> 00:35.330 to do it. 00:36.210 --> 00:43.170 So many Seelie tools rely on environment variables in order to reduce the configuration that you have 00:43.170 --> 00:44.900 to put in when using the seal. 00:45.630 --> 00:48.360 The reason for that is authentication. 00:48.360 --> 00:54.180 Information, for example, will need to be placed in each and every command and that can make the command 00:54.360 --> 00:57.510 longer and not necessarily for a good reason. 00:57.810 --> 01:00.570 So if you look at this command, you can see it's pretty simple. 01:00.630 --> 01:06.060 Now, if we had to add additional parameters with the username and ELGAN, it will make the comment 01:06.060 --> 01:06.450 longer. 01:07.500 --> 01:15.180 And in this case, Serge knows how to look for the username and the talk, but this doesn't happen randomly, 01:15.180 --> 01:19.260 so search will not start like looking through all the environment variables. 01:19.530 --> 01:23.780 It will look for a specific environment variable or that specific value. 01:24.030 --> 01:26.370 And if that information is present, it will use it. 01:26.740 --> 01:32.670 Otherwise, if Surge or other Sellitto will not find the predefined environment variable that he's looking 01:32.670 --> 01:41.040 for and it will either use information from the Seelie or it will say, hey, you haven't provided any 01:41.040 --> 01:44.490 notification information or any other information that maybe is required. 01:46.430 --> 01:52.820 As with many tools, the only way to know how exactly to name the environment variables is to look at 01:52.820 --> 01:55.220 the documentation in a case of search. 01:55.250 --> 01:59.210 This is a bit hidden and it's actually mixed up with other documentation. 01:59.600 --> 02:04.820 But you can see here that this is documented in the sense that says you can create one environment variable 02:04.820 --> 02:08.630 called search under login and set it to the email address. 02:08.630 --> 02:09.590 You want to use search. 02:09.800 --> 02:17.030 And again, this search token, what's important to notice is that you need to name the environment 02:17.030 --> 02:19.480 variable exactly as search expected. 02:19.910 --> 02:24.440 So, for example, if you give here a different name for the logging on, a different name for the token, 02:24.440 --> 02:29.710 or you just say token and so do not know that token is meant for search. 02:29.720 --> 02:33.050 So you have to give the exact name as in the documentation. 02:34.090 --> 02:39.610 So the main takeaway here is that many zeolite tools will rely on environment variables to get some 02:39.610 --> 02:45.670 information, and if you specify those environment variables as the zeolite will expect them, then 02:45.670 --> 02:48.220 it will automatically look for them and use them. 02:48.670 --> 02:53.290 This is a very good way on how you can reduce the length of the air configuration, the length of the 02:53.290 --> 02:55.690 comment that you are using in your pipeline.