Looking back again at our configuration and at the command that we have executed, there's still a question
regarding how exactly does Surján know to use the tokens and a username that we have provided as environment
variables?
Because if you look at the command, you would only see that we instructed the location of the project
and the name of the domain.
But after that, apparently Serj knew what to deploy, which is the account, and had to right permission
to do it.
So many Seelie tools rely on environment variables in order to reduce the configuration that you have
to put in when using the seal.
The reason for that is authentication.
Information, for example, will need to be placed in each and every command and that can make the command
longer and not necessarily for a good reason.
So if you look at this command, you can see it's pretty simple.
Now, if we had to add additional parameters with the username and ELGAN, it will make the comment
longer.
And in this case, Serge knows how to look for the username and the talk, but this doesn't happen randomly,
so search will not start like looking through all the environment variables.
It will look for a specific environment variable or that specific value.
And if that information is present, it will use it.
Otherwise, if Surge or other Sellitto will not find the predefined environment variable that he's looking
for and it will either use information from the Seelie or it will say, hey, you haven't provided any
notification information or any other information that maybe is required.
As with many tools, the only way to know how exactly to name the environment variables is to look at
the documentation in a case of search.
This is a bit hidden and it's actually mixed up with other documentation.
But you can see here that this is documented in the sense that says you can create one environment variable
called search under login and set it to the email address.
You want to use search.
And again, this search token, what's important to notice is that you need to name the environment
variable exactly as search expected.
So, for example, if you give here a different name for the logging on, a different name for the token,
or you just say token and so do not know that token is meant for search.
So you have to give the exact name as in the documentation.
So the main takeaway here is that many zeolite tools will rely on environment variables to get some
information, and if you specify those environment variables as the zeolite will expect them, then
it will automatically look for them and use them.
This is a very good way on how you can reduce the length of the air configuration, the length of the
comment that you are using in your pipeline.