1
00:00:03,000 --> 00:00:10,020
In this, like we have a look on how we can manage secrets when using Gottleib, you generally do not

2
00:00:10,020 --> 00:00:18,750
want to keep any credentials and generally even usernames or passwords or tokens, anything that is

3
00:00:18,750 --> 00:00:19,410
sensitive.

4
00:00:19,410 --> 00:00:24,850
You do not want to commit that in your pipelines or in any files or something like that.

5
00:00:25,200 --> 00:00:31,080
So anything that goes inside it shouldn't contain tokens, passwords, secrets or something like that.

6
00:00:31,800 --> 00:00:37,020
And get Lexia offers us a convenient way in order to store such secrets.

7
00:00:38,070 --> 00:00:44,130
Now, the goal is to be able to use catalepsy in order to deploy the website to search.

8
00:00:44,940 --> 00:00:52,170
And as you have seen, we have this interactive interface where you using our email and password.

9
00:00:52,800 --> 00:00:57,240
And this is something that's, of course, not available in Getler because you cannot interact with

10
00:00:57,240 --> 00:01:00,120
this tool and start typing in things.

11
00:01:00,900 --> 00:01:05,730
And generally you do not want to use username and password in order to do deployments.

12
00:01:06,540 --> 00:01:10,550
And such tools offer the possibility of using tokens in order to login.

13
00:01:10,950 --> 00:01:17,400
So instead of using your username and password, you supply this token and you can even look later revoked

14
00:01:17,400 --> 00:01:17,970
a token.

15
00:01:18,660 --> 00:01:23,070
If, for whatever reason you think it has been compromised without actually changing your username and

16
00:01:23,070 --> 00:01:26,250
password, without exposing them in this case.

17
00:01:27,330 --> 00:01:30,300
So let's call first the search and generate a token.

18
00:01:32,230 --> 00:01:39,040
I still have my seal opened and what I need to do is to type in search Galchen.

19
00:01:43,670 --> 00:01:49,400
And I'm sort of still locked in with search and search has then generated this token for me.

20
00:01:51,310 --> 00:01:54,760
Let's go to get dot com and see where we can manage the cigarettes.

21
00:01:58,300 --> 00:02:04,570
From the sidebar on your project, you should be able to see it right here at the bottom settings and

22
00:02:04,570 --> 00:02:07,570
if you hover over it, just go to secede.

23
00:02:10,650 --> 00:02:16,500
And right here in the middle, you'll see environment variables and environment variables, as it says

24
00:02:16,500 --> 00:02:23,850
here, are applied to environments when using the runner so we can define here variables and these variables

25
00:02:23,850 --> 00:02:27,930
will be injected by Gottleib and will be available in the runner.

26
00:02:28,320 --> 00:02:31,620
So let's expand this and add our secrets here.

27
00:02:32,520 --> 00:02:35,250
So we're going to create two different variables.

28
00:02:36,160 --> 00:02:41,480
I'm going to use a variable called Surge Log-in and this will be our account.

29
00:02:42,240 --> 00:02:45,420
So your e-mail address that you have used to register for search.

30
00:02:47,770 --> 00:02:55,180
And the second environment variable that will create is surge token, so surge underscore token, and

31
00:02:55,180 --> 00:02:58,510
this is the token that you have been given in the Seelie.

32
00:03:03,260 --> 00:03:05,390
So let's go ahead and save these variables.

33
00:03:06,930 --> 00:03:11,520
Once you have saved this information, you will no longer seat, but just in case you want to check,

34
00:03:11,520 --> 00:03:16,950
if everything is still OK, you can click here or reveal values and you will see the original values.

35
00:03:20,270 --> 00:03:21,270
So that's about it.

36
00:03:21,290 --> 00:03:27,620
This is how you can save and manage secrets in your lap by using environment variables and as I said,

37
00:03:27,620 --> 00:03:31,130
this environmental variables will be later available when you're running the jobs.