WEBVTT

1
00:00.000 --> 00:04.000
So now that we have recapped the basics of compression and archives,

2
00:04.000 --> 00:08.000
let's now take a look at an Ansible module that can help us perform these tasks

3
00:08.000 --> 00:08.000
.

4
00:08.000 --> 00:12.560
So if you happen to search for Ansible Archive module and you click on this top

5
00:12.560 --> 00:13.520
link right here,

6
00:13.520 --> 00:17.270
so the name of the module that we're going to be using is community.general.

7
00:17.270 --> 00:18.320
archive and if we scroll

8
00:18.320 --> 00:22.720
on down we can see here this is part of the community.general collection. So if

9
00:22.720 --> 00:23.040
you have not

10
00:23.040 --> 00:26.340
already installed this collection, which by this point you probably already

11
00:26.340 --> 00:26.880
should have,

12
00:26.880 --> 00:30.720
but nevertheless if you're not, then you can get this collection by just simply
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:26.880 --> 00:30.720
but nevertheless if you're not, then you can get this collection by just simply

13
00:30.720 --> 00:31.200
typing in the

14
00:31.200 --> 00:35.870
command Ansible Galaxy Collection Install community.general. Now let's go down

15
00:35.870 --> 00:37.520
here to the synopsis here.

16
00:37.520 --> 00:41.140
Now it says here this is going to allow us to create or extend an archive and

17
00:41.140 --> 00:41.760
now crucially

18
00:41.760 --> 00:47.020
here it says the source and the archive are going to be on the remote host and

19
00:47.020 --> 00:48.080
the archive is not

20
00:48.080 --> 00:51.880
copied to the local host. So pretty much here as we know we have our Ansible

21
00:51.880 --> 00:52.880
control nodes and

22
00:52.880 --> 00:56.150
let's say we have our managed device such as the blue box that we're going to

23
00:56.150 --> 00:57.120
be managing with

24
00:57.120 --> 01:01.590
Ansible. If we want to perhaps create an archive on this particular device here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:57.120 --> 01:01.590
Ansible. If we want to perhaps create an archive on this particular device here

25
01:01.590 --> 01:01.760
,

26
01:01.760 --> 01:08.320
the actual files involved such as let's maybe say file 1.txt and file 2.txt,

27
01:08.320 --> 01:08.880
the actual are going

28
01:08.880 --> 01:13.600
to live on this particular device when the archiving happens. The archive is

29
01:13.600 --> 01:15.120
not generated from files

30
01:15.120 --> 01:19.070
on the actual control node and then copied over it's pretty much on the

31
01:19.070 --> 01:20.800
existing box. Now just to

32
01:20.800 --> 01:26.400
be clear here if you do happen to have particular files on this device here

33
01:26.400 --> 01:26.960
that you want to be

34
01:26.960 --> 01:31.740
compressed and present on the target device then you can still do this. All you
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:26.960 --> 01:31.740
compressed and present on the target device then you can still do this. All you

35
01:31.740 --> 01:32.480
would have to do

36
01:32.480 --> 01:36.340
would be to copy the files over to the target first using the Ansible copy

37
01:36.340 --> 01:37.680
module once they now

38
01:37.680 --> 01:42.230
exist on this device here you can now use this particular module to archive and

39
01:42.230 --> 01:43.120
compress them.

40
01:43.120 --> 01:47.120
So just keep that distinction in your mind. So let's look at some parameters

41
01:47.120 --> 01:48.000
here if we look at the

42
01:48.000 --> 01:52.990
desk parameter as we can see here what we have to provide is a path pretty much

43
01:52.990 --> 01:53.760
where on the file

44
01:53.760 --> 01:58.110
system to be want the archive to reside. Now notice here this is something very

45
01:58.110 --> 01:58.880
very important.

46
01:58.880 --> 02:02.890
It says here that the parent directory must exist on the remote host pretty
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
01:58.880 --> 02:02.890
It says here that the parent directory must exist on the remote host pretty

47
02:02.890 --> 02:04.160
much on the target.

48
02:04.160 --> 02:07.680
If that does not exist then you will have to create this directory structure

49
02:07.680 --> 02:08.720
before you happen to

50
02:08.720 --> 02:12.410
launch this particular module and by the way notice is that if the destination

51
02:12.410 --> 02:13.360
archive already

52
02:13.360 --> 02:17.390
exists it's going to be truncated and effectively overwritten we'll just write

53
02:17.390 --> 02:18.560
over that completely.

54
02:18.560 --> 02:22.480
Now this module also gives us the option to specify compression as well and as

55
02:22.480 --> 02:23.200
we can see here this

56
02:23.200 --> 02:26.810
is done via the format parameter and all we do here is specify the type of

57
02:26.810 --> 02:28.000
compression we want to

58
02:28.000 --> 02:32.210
use so we can use busy too. We can just create a regular tarball which is not
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:28.000 --> 02:32.210
use so we can use busy too. We can just create a regular tarball which is not

59
02:32.210 --> 02:33.360
actually going to

60
02:33.360 --> 02:37.530
be compressed. We can specify xz compression and we can also specify zip

61
02:37.530 --> 02:39.280
compression which is also

62
02:39.280 --> 02:43.430
very useful for Windows based devices that you happen to be managing. Now the

63
02:43.430 --> 02:44.080
resultant

64
02:44.080 --> 02:48.030
fail system object that we're going to create the actual archive we can also

65
02:48.030 --> 02:49.120
attach permissions

66
02:49.120 --> 02:53.400
to this okay and we do this via the mode parameter. Originally this would be

67
02:53.400 --> 02:54.480
specified via

68
02:54.480 --> 02:59.440
octonotations that would be on numeric values such as 755 or if you want to

69
02:59.440 --> 03:00.480
also include special
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
02:59.440 --> 03:00.480
also include special

70
03:00.480 --> 03:05.710
permissions that could be 1 6 4 4 whatever it may be using the four digits but

71
03:05.710 --> 03:06.480
in later versions

72
03:06.480 --> 03:10.440
of Ansible at either version you should have we can also have support for

73
03:10.440 --> 03:11.760
symbolic notation so we

74
03:11.760 --> 03:15.770
can just specify read write and execute as we so wish. We also have the option

75
03:15.770 --> 03:17.120
here to specify the

76
03:17.120 --> 03:21.700
owner pretty much when we create that object who should actually own it. This

77
03:21.700 --> 03:22.640
parameter acts as

78
03:22.640 --> 03:26.610
an abstraction layer for the tone command basically and now we move down to our

79
03:26.610 --> 03:27.760
require parameter so

80
03:27.760 --> 03:31.440
we're going to absolutely have to specify this if we want the module to operate
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:27.760 --> 03:31.440
we're going to absolutely have to specify this if we want the module to operate

81
03:31.440 --> 03:32.800
. Now don't get this

82
03:32.800 --> 03:37.980
confused with the desk parameter okay. In the case here the path parameter is

83
03:37.980 --> 03:38.720
going to allow to

84
03:38.720 --> 03:42.490
supply a list object and the information that we're going to supply here is

85
03:42.490 --> 03:44.000
going to be the remote

86
03:44.000 --> 03:48.770
absolute path for the fail that you want to compress or archive or the globe

87
03:48.770 --> 03:49.680
for the multiple

88
03:49.680 --> 03:54.170
files you want to compress or archive or if we so wish a list of multiple

89
03:54.170 --> 03:55.600
different paths whereby

90
03:55.600 --> 04:00.600
we can specify fails to compress or archive. So say for example you've got file
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
03:55.600 --> 04:00.600
we can specify fails to compress or archive. So say for example you've got file

91
04:00.600 --> 04:01.760
1 dot txt and

92
04:01.760 --> 04:07.520
file 2 dot txt if you want to compress and archive these particular files you

93
04:07.520 --> 04:09.360
specify that via the

94
04:09.360 --> 04:14.120
path parameter right here. If you want to use these files and create an archive

95
04:14.120 --> 04:15.040
called well I don't

96
04:15.040 --> 04:20.920
know that just maybe say my data dot tar dot busy this particular option would

97
04:20.920 --> 04:22.640
be specified via the

98
04:22.640 --> 04:26.930
desk parameter you see big big distinction. Now again scrolling on down you can

99
04:26.930 --> 04:27.280
go through

100
04:27.280 --> 04:31.230
many different options we have options for security enhanced Linux so if you
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
04:27.280 --> 04:31.230
many different options we have options for security enhanced Linux so if you

101
04:31.230 --> 04:32.320
want to also configure

102
04:32.320 --> 04:36.050
particular se Linux security context then you can do so via a variety of

103
04:36.050 --> 04:37.360
different ways via the

104
04:37.360 --> 04:42.170
se level parameter se role se type that type of thing okay. So let's go back to

105
04:42.170 --> 04:43.040
our terminal

106
04:43.040 --> 04:46.850
right now and we'll begin using this particular module within a playbook so let

107
04:46.850 --> 04:47.440
me go to my

108
04:47.440 --> 04:51.740
blue box device right here I'll open up a terminal and inside of this directory

109
04:51.740 --> 04:52.800
right here all that

110
04:52.800 --> 04:57.520
we'll do is I'll create a little file called my file 1 dot txt I'll just say

111
04:57.520 --> 04:59.120
this is my file 1

112
04:59.120 --> 05:03.700
and I'll just write and quit and let's also create one called my file 2 dot txt
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
04:59.120 --> 05:03.700
and I'll just write and quit and let's also create one called my file 2 dot txt

113
05:03.700 --> 05:04.800
once again super

114
05:04.800 --> 05:09.570
debircrative I'll just say this is my file 2 and save you of course we have

115
05:09.570 --> 05:10.400
these two devices or

116
05:10.400 --> 05:15.080
rather these two files on the remote device that we want to manage with Ansible

117
05:15.080 --> 05:16.160
file 1 and file 2

118
05:16.160 --> 05:20.840
okay let's now go back to our control nodes and now we can begin writing our

119
05:20.840 --> 05:21.840
playbooks let's just

120
05:21.840 --> 05:26.240
call this play 1 dot yml so let's go into insert mode right here have our free

121
05:26.240 --> 05:27.360
hyphens at the top

122
05:27.360 --> 05:32.200
give this playbook a name and we'll just call this play 1 testing the archive
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
05:27.360 --> 05:32.200
give this playbook a name and we'll just call this play 1 testing the archive

123
05:32.200 --> 05:33.280
module now who are

124
05:33.280 --> 05:36.940
the hosts that I want to target if I so wish I could target all devices in my

125
05:36.940 --> 05:37.840
topology in my

126
05:37.840 --> 05:41.780
case here I'm just going to target the blue box okay now I don't want to gather

127
05:41.780 --> 05:42.560
facts that is not

128
05:42.560 --> 05:45.500
going to be useful so I'm just going to configure that to be false in order to

129
05:45.500 --> 05:47.040
save time for execution

130
05:47.040 --> 05:50.780
and now to specify the tasks that I want to create here so the first task I'll

131
05:50.780 --> 05:52.560
just call create archive

132
05:52.560 --> 05:57.200
of some text files now what I'm actually going to use here well we know the

133
05:57.200 --> 05:57.920
fully qualified

134
05:57.920 --> 06:02.640
collection name of this module is community dot general dot archive remember to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
05:57.920 --> 06:02.640
collection name of this module is community dot general dot archive remember to

135
06:02.640 --> 06:03.600
install this with

136
06:03.600 --> 06:07.560
Ansible Galaxy if you don't have this module and now I'm going to specify the

137
06:07.560 --> 06:08.560
path now the path

138
06:08.560 --> 06:12.800
is required after all and this is going to be all of the files that I want to

139
06:12.800 --> 06:14.400
be targeting right here

140
06:14.400 --> 06:18.560
now I can supply this as a list object if I so wish so I can just say my file

141
06:18.560 --> 06:19.120
in fact let me give

142
06:19.120 --> 06:24.860
the full path I'll say home nuggets user my file 1 dot txt and the second one

143
06:24.860 --> 06:27.040
will be home nugget user

144
06:27.040 --> 06:32.460
my file 2 dot txt now specify the destination pretty much what is the file that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
06:27.040 --> 06:32.460
my file 2 dot txt now specify the destination pretty much what is the file that

145
06:32.460 --> 06:33.360
I want to create so

146
06:33.360 --> 06:37.920
again I'll put it in the same directory and I'll just call this my archive dot

147
06:37.920 --> 06:40.560
tar dot gz okay so

148
06:40.560 --> 06:44.160
basically I want to be combining both of these files into a singular file and I

149
06:44.160 --> 06:44.640
also want to

150
06:44.640 --> 06:48.770
compress it with gzip compression now remember the way we can specify the

151
06:48.770 --> 06:50.400
compression type is via

152
06:50.400 --> 06:54.470
the format parameter now as per the option right here notice the valid values

153
06:54.470 --> 06:55.840
if you want to specify

154
06:55.840 --> 07:00.670
bzip to compression we actually just specify bz2 and if you want gzip
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

154
06:55.840 --> 07:00.670
bzip to compression we actually just specify bz2 and if you want gzip

155
07:00.670 --> 07:03.040
compression you just say gz

156
07:03.040 --> 07:07.760
not gzip now as we can see here by default the compression is going to be gzip

157
07:07.760 --> 07:08.240
so we actually

158
07:08.240 --> 07:12.190
don't have to be explicit in this case here but if you so wish then you can do

159
07:12.190 --> 07:13.040
so so just in the

160
07:13.040 --> 07:16.100
interest of making the playbook more readable I will just explicitly specify

161
07:16.100 --> 07:17.120
that I'm using gz

162
07:17.120 --> 07:21.140
compression okay so let's just press colon wq to write and quit I will say

163
07:21.140 --> 07:22.400
answer will play book

164
07:22.400 --> 07:26.450
play 1 dot yml and to answer open it appears I actually don't happen to have

165
07:26.450 --> 07:27.440
the community dot

166
07:27.440 --> 07:30.770
general archive on my particular playbook because I've used an old virtual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

166
07:27.440 --> 07:30.770
general archive on my particular playbook because I've used an old virtual

167
07:30.770 --> 07:31.920
machine right here so

168
07:31.920 --> 07:35.250
let me just type in the answer will galaxy collection install community dot the

169
07:35.250 --> 07:36.240
general apologies about

170
07:36.240 --> 07:39.930
that just give it a moment now I have the collection installed let's try to

171
07:39.930 --> 07:41.120
read on the playbook again

172
07:41.120 --> 07:45.200
so the playbook kicks off and as we can see as per the recap we have a change

173
07:45.200 --> 07:46.080
on the device

174
07:46.080 --> 07:50.470
and if we now go back to our blue box if I do an LS notice we happen to have a

175
07:50.470 --> 07:51.680
compressed archive

176
07:51.680 --> 07:54.900
of the fails right here so let's just do it we did in the previous video let's

177
07:54.900 --> 07:55.520
just remove

178
07:55.520 --> 08:00.630
these particular files fail 1 and my fail 2 dot txt so all that is left right
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

178
07:55.520 --> 08:00.630
these particular files fail 1 and my fail 2 dot txt so all that is left right

179
08:00.630 --> 08:01.600
now is the actual

180
08:01.600 --> 08:07.130
archive if I want to undo that what I can do is say tar dot x to extract the

181
08:07.130 --> 08:08.560
tarball I will say

182
08:08.560 --> 08:13.720
z because that is how we extract the tarball using gzip compression via tar and

183
08:13.720 --> 08:14.080
then say

184
08:14.080 --> 08:18.690
f for the fail and target the fail my archive dot tar dot gz if I hit enter if

185
08:18.690 --> 08:20.240
I do an LS now we

186
08:20.240 --> 08:24.770
have these fails back and again if I just cat them and to enter there is fail 1

187
08:24.770 --> 08:25.840
the content is still

188
08:25.840 --> 08:29.920
the same and I can't fail to the content has not been modified now we notice

189
08:29.920 --> 08:30.720
that from the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

189
08:29.920 --> 08:30.720
that from the

190
08:30.720 --> 08:34.940
documentation we had reference to the concept of globbing pretty much all glob

191
08:34.940 --> 08:35.920
bing is going to allow

192
08:35.920 --> 08:40.420
us to do it's going to allow us to specify particular fail paths by utilizing

193
08:40.420 --> 08:41.360
very particular

194
08:41.360 --> 08:45.140
patterns so as opposed to having to feed in every single individual file that

195
08:45.140 --> 08:45.920
you want to be a

196
08:45.920 --> 08:50.400
part of this particular archive you can use a fail globe to effectively match

197
08:50.400 --> 08:51.360
on a particular

198
08:51.360 --> 08:55.360
pattern now the most common fail globbing technique is to use the asterisk so

199
08:55.360 --> 08:56.000
let's maybe say you

200
08:56.000 --> 09:00.980
wanted to archive all files that happen to end in dot txt you could say aster
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

200
08:56.000 --> 09:00.980
wanted to archive all files that happen to end in dot txt you could say aster

201
09:00.980 --> 09:01.920
isk dot txt which

202
09:01.920 --> 09:05.650
pretty much means anything so long as it ends in dot txt that would match and

203
09:05.650 --> 09:06.400
now you could

204
09:06.400 --> 09:10.700
create an archive of all those dot txt files or you could specify say for

205
09:10.700 --> 09:11.920
example the question

206
09:11.920 --> 09:15.720
mark sign or question mark character should I say which is going to allow you

207
09:15.720 --> 09:16.560
to match any

208
09:16.560 --> 09:21.730
particular character so say for example I did fail question mark dot txt this

209
09:21.730 --> 09:22.880
here would match

210
09:22.880 --> 09:27.500
on any single character right here so if I happen to have a fail called let's

211
09:27.500 --> 09:29.120
maybe say fail one dot

212
09:29.120 --> 09:34.430
txt that would match if I happen to have fail five dot txt that would also
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

212
09:29.120 --> 09:34.430
txt that would match if I happen to have fail five dot txt that would also

213
09:34.430 --> 09:36.240
match because it is one

214
09:36.240 --> 09:41.810
single character or matching here however if I had a fail called fail 10 dot t

215
09:41.810 --> 09:42.400
xt then that

216
09:42.400 --> 09:45.520
actually would not match the pattern because what we're actually wanting here

217
09:45.520 --> 09:46.560
is the word fail

218
09:46.560 --> 09:51.630
followed by any single character immediately followed by dot txt this does not

219
09:51.630 --> 09:52.400
follow this

220
09:52.400 --> 09:56.420
particular format because we have two new characters so that is all we're

221
09:56.420 --> 09:57.600
really talking about with

222
09:57.600 --> 10:01.490
respect to globbing we're talking about using patterns to match particular file
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

222
09:57.600 --> 10:01.490
respect to globbing we're talking about using patterns to match particular file

223
10:01.490 --> 10:02.240
paths if you

224
10:02.240 --> 10:05.590
want to see more paths that you can specify then by all means I would encourage

225
10:05.590 --> 10:06.480
you to research

226
10:06.480 --> 10:10.030
more advanced lennox globbing techniques but for now we're not going to spend

227
10:10.030 --> 10:11.440
too much time on it

228
10:11.440 --> 10:14.750
let me instead just demonstrate that this technique can be used directly within

229
10:14.750 --> 10:14.880
the

230
10:14.880 --> 10:19.760
Ansible playbook so let's go back again so let's remove the my archive dot txt

231
10:19.760 --> 10:20.480
and what I will do

232
10:20.480 --> 10:25.010
now is I'll create one called my file 10 dot txt to use example that I just

233
10:25.010 --> 10:26.000
said there so let's

234
10:26.000 --> 10:30.200
just say this is fail 10 just write and quit so here we have our three text
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

234
10:26.000 --> 10:30.200
just say this is fail 10 just write and quit so here we have our three text

235
10:30.200 --> 10:31.680
files let's go in to

236
10:31.680 --> 10:35.020
our playbook once again and all I'm going to do here is as opposed to

237
10:35.020 --> 10:36.720
specifying multiple individual

238
10:36.720 --> 10:40.210
paths all I want to do is I want to use this globbing technique so in this

239
10:40.210 --> 10:41.120
particular example

240
10:41.120 --> 10:44.660
here let me just change this to a question mark and let's also change the

241
10:44.660 --> 10:46.720
compression to be bz to

242
10:46.720 --> 10:50.470
this time for a little bit of difference and again we'll change the name of the

243
10:50.470 --> 10:52.480
extension to be bz2 as

244
10:52.480 --> 10:56.610
well so let's see how this actually shakes out let's just press colon wq to

245
10:56.610 --> 10:57.600
rank it and now see

246
10:57.600 --> 11:01.620
Ansible playbook on play one and to answer now we create a new archive let's go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

246
10:57.600 --> 11:01.620
Ansible playbook on play one and to answer now we create a new archive let's go

247
11:01.620 --> 11:02.400
back and see the

248
11:02.400 --> 11:06.590
results case if I do an LS we can see we have created the new archive file

249
11:06.590 --> 11:07.840
right here if say for

250
11:07.840 --> 11:14.880
example I move my file 1 dot txt and my file 2 as well as my file 10 dot txt

251
11:14.880 --> 11:15.680
and I'll put it into

252
11:15.680 --> 11:18.620
another directory just so it's out the road let's maybe go into the documents

253
11:18.620 --> 11:19.760
directory okay so now

254
11:19.760 --> 11:22.870
they're not here and what I will do now is extract the archive and we'll

255
11:22.870 --> 11:24.480
actually see which files are

256
11:24.480 --> 11:29.210
inside of that archive so if I say tar dot x to extract lower case j because it

257
11:29.210 --> 11:30.720
is bz2 compression
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

257
11:29.210 --> 11:30.720
is bz2 compression

258
11:30.720 --> 11:35.450
and specify the file with the f switch and then say my archive dot tar dot bz2

259
11:35.450 --> 11:36.640
and to answer

260
11:36.640 --> 11:41.260
now we extract into an LS check this out right here notice the contents are

261
11:41.260 --> 11:43.440
only my file 1 dot txt

262
11:43.440 --> 11:49.450
and my file 2 dot txt the my file 10 dot txt file was not included whereas if I

263
11:49.450 --> 11:50.080
just happened to

264
11:50.080 --> 11:54.620
remove my archive as well as the files and I go into my documents right here

265
11:54.620 --> 11:55.600
here are the files

266
11:55.600 --> 11:59.520
right here and I'll just say move everything back a directory let's go back out

267
11:59.520 --> 12:00.560
to an LS there are
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

267
11:59.520 --> 12:00.560
to an LS there are

268
12:00.560 --> 12:04.290
the three files I now go back into my playbook and I change the globbing

269
12:04.290 --> 12:05.680
technique to specify that

270
12:05.680 --> 12:09.670
it's going to be an asterisk which will match any characters or any amount of

271
12:09.670 --> 12:10.720
characters if I

272
12:10.720 --> 12:15.200
now rerun it and I hit enter we now create the archive once again but this time

273
12:15.200 --> 12:16.320
let me just remove

274
12:16.320 --> 12:20.920
all of my files and then dot txt so all we have now is the actual archive let's

275
12:20.920 --> 12:22.240
just say tar dot x

276
12:22.240 --> 12:27.760
to extract lower case j then if I now specify my archive dot tar dot bz2 and to

277
12:27.760 --> 12:29.440
enter do an LS

278
12:29.440 --> 12:33.460
now we can see here all three files are present because effectively all three
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

278
12:29.440 --> 12:33.460
now we can see here all three files are present because effectively all three

279
12:33.460 --> 12:34.560
files were matched

280
12:34.560 --> 12:39.150
on the globbing pattern and thus a part of the my archive dot tar dot bz2

281
12:39.150 --> 12:40.080
archive file