►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
What's
this,
it's
just
stocks
right,
oh,
this
is
for
the
Azure
storage
account
stuff.
Yes,
do
we
want
to
coordinate
this,
or
is
it
fine
to
do?
We
want
to
mention
in
which
version
this
is
available.
B
C
This
wasn't
documented
no
docs
I
was
looking
into
this
one.
That's
why
I
added
some
documentation
so
yeah
according
to
the
code,
it's
always
September
first
and
it
has
a
default
value,
so
you
can
change
it.
C
It's
a
little
bit
could
be
improved,
but
I
didn't
have
a
good
idea.
How.
A
A
Magic
seems
to
be
like,
like
the
just
a
clone
from
the
other.
Was
it
parametric
solution.
C
A
A
So
I
see
so
they
are
building
their
their
own
tanzo
integration
thing
I,
guess
yeah!
That's
probably
what
this
is
I
mean
it's.
A
A
Both
accounts
thanks,
probably
not
the
boss.
B
A
A
B
A
Or
the
architecture
that
was
chosen,
it's
just
yeah
a
bit
horrible
to
look
at,
but
that's
what
we.
What
and
what's
the
secret
used
for?
B
Oh
yeah,
so
it's
a
comment
about
the
this
scroll
down
a
little
bit.
B
Yes
here
so
I
see
in
csrisio,
I,
Lobster,
client
implementation,
and
there
is
one
line
so
like
here.
The
path
equals
to
which
is
a
file
can
respond
to
the
passcore,
and
the
ENC
comment
is
saying:
in
Ruby:
1.8
file
does
not
and
doesn't
respond
to
the
passcore
I'm,
not
sure
whether
someone
will
still
use
the
Ruby
1.8
or
not.
If
we
can
confirm
that
1.8
is
never
used
it
anymore.
So
I
can
edit.
B
C
C
A
C
A
B
C
A
Adding
it
to
the
Builder
right,
yeah
yeah,
just
probably
one
stage:
yes
yeah,
that
makes
sense.
Okay,.
A
B
C
C
A
I
didn't
need
to
do
some
digging
in
slack
I.
Believe
there
were
at
some
point
was
a
discussion
about
it.
That's
why
I
wanted
to
just
focus
on
this
one,
because
I
know
for
sure
about
this.
One.
A
A
So
he
also
adds
Joseph.
B
A
B
A
A
I
think
Joseph
built
that,
where
he's
doing
like
a
Bosch
deployment
and
then
orphans
the
VM
and
then
starts
like
sshing
the
agent
on
there
and
run
some
integration
tests
against
it,
which
I
think
is
even
better
but
I,
don't
know
if
that,
because
then
like
you,
can
actually
verify
that
all
the
functionality
works
right.
C
I
think
of
this
in
the
bush,
repo
somewhere,
is
that
in
the
bush
repo,
it's
documented.
If
you
go
in
running
tests
in
this
Posh
agent,
if
you
in
the
Porsche
agent
running
a
test
and
on
the
integration
test,
I
think
it's
documented
agent,
repo,
okay,
yeah,
there's
somewhere
around
interest
Below
in
the
readme.
C
A
So
this
will
be
like
a
fast
like
this
is
basically
what
you're
doing,
but
then
we're
also
actually
running
the
the
integration
test
to
verify
that
it
actually
works
right.
A
B
Yes,
yes,
this
I
would
say
that
so
like
test
all
the
stuff,
but
sometimes
for
example,
if
we
are
not
familiar
with
the
code,
then
we
change
the
code
a
bit.
If
we
run
the
integration
testers
that
may
it
may
cost
for
like
one
hour
to
get
the
result
and
in
the
end
we
get
a
arrow.
And
then
we
need
to
change
the
code
again
and
to
run
the
integration
test
which
costs
time.
But
if
we
have
and
the
way
that
we've
document
it,
then
we
can
get
the
arrow
faster
right.
B
C
C
A
Oh,
it's
a
new
version,
new
documents.
You
know
it's
in
Docs.
A
Yeah
I
will
ask
Joseph
to
review
because
he
has
like
touched
this
stuff,
the
last
he
had
done
that,
like
major
refactor
through
the
test,
so
maybe
he
has.
He
has
more
opinions
on
this.
A
Okay:
let's
go
over
open
issues.
A
Thanks,
let's
put
this
in
discussion:
wait
yeah.