►
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
B
B
B
Let's
do
it.
I
have
put
a
few
points
into
this
document
on
the
agenda.
Let's
start
with
the
first
one,
that's
the
credentials
for
the
three
but
uses.
B
A
B
Part
of
this
org
and
yeah,
we
can't
continue
here
because
we
do
not
have
the
potentials
and
I
mean.
There's
one
thing
you
could
maybe
organize
somehow
that
somebody
accepts
invitation,
and
the
second
thing
is
we
should
I
guess
eventually
bring
these
credentials
somehow
into
yeah
into
the
community
and
I,
don't
know
into
the
setup
or
wherever
it's
a
safe
place.
Is
that
something
that
Johan
can
then
organize?
B
A
A
If,
if
it's
a
I
can't
remember
if
he
replaced
it
with
a
whole
new
bot
or
whether
he
just
changed
the
like
committer
title,
if
he
did
the
former,
then
I
don't
have
the
credentials
for
the
new
bot.
I
have
the
credentials
for
the
old
bot
or
the
old
Bots
I
should
say,
because
they
used
to
be
three
I.
Think.
B
He
just
he
was
the
old
ones,
because
the
pipelines
are
still
working,
everything
is
fine
and
and
Johan
doesn't
have
any
credential,
so
he
could
not
change
anything.
That's
what
he
told
me.
Okay,.
A
B
Now
is
the
orc
automation
runs
and
tries
to
assign
these
three
Bots
into
a
certain
team
in
this,
what
was
it
called
work
group
up,
runtime
deployment
spots,
team.
A
B
And
this
one
fails
because
the
bot
user
itself
needs
to
accept
the
invitation.
A
I
may
not
be
able
to
sign
in
hang
on
they
they're
all.
They
all
use
an
old,
pivotal
email
address.
B
A
B
Right
yeah
already
right,
but
the
automation
now
always
lists
them.
If
you
go,
let's
say
to
this:
URL
I
will
put
it
in
the
chat.
A
A
A
B
B
I
I
would
just
send
it.
It
looks
a
bit
strange
now,
but
these
are
the
names
I
try
to
copy,
but
it's
a
web
page
and
then
you
get
everything
a
little
bit
this
formatted.
A
Problem
well,
yeah
I,
don't
know
what
I
just
received
it
sent
me
like
the
profile
pictures
of
the
bot
accounts.
A
Okay,
doesn't
it's
very
cool
regardless
I
think
I
know
yeah.
It
just
sent
me
four
pictures
of
the
profile
pictures
of
the
body
cam
regardless
the
with
the
link
that
I
sent
I
can
see
the
three
that
we're
trying
to
add
exactly.
Is
this
other
screen
yeah
I
I
can't
log
in
because
they
require,
like
I,
said
they're
they're,
all
using
an
old
pivotal
account
with
two-factor
auth
set
up
that
I
can't
access,
so
we'll
have
to
talk
to
Dave
to
log
in
and
and
authorize
the
authorized.
A
Cloud
Foundry
I
think
at
that
point.
It's
probably
a
good
idea
to
either
change
the
emails
on
these
accounts
or
just
create
a
new
bot
GitHub
that
we
could
use
with
with
this
Ard
working
group
as
the
bot.
B
A
B
A
B
A
A
A
B
Good
I
can
text
it
with
me
and
asking
the
TOC
it's
a
good
question,
but
anyway
just
to
unblock
it.
Maybe
Dave
can
approve
it
for
now,
but
the
problem
is
they're.
Not
so,
if
that's.
A
B
B
A
Where,
where
is
the
new
red
hub
hosted
these
days?
B
B
Meanwhile,
as
separate
project,
that's
called
it's
part
of
the
working
group,
something
with
infrastructure,
I.
A
A
I've
searched
and
I
found
app
runtime
deployments
infrastructure
in
Cloud,
Foundry
I,
don't
see
a
script
or
anything
to
access
cred
Hub,
though
so
I'm
not
sure
how
I'm
supposed
to
do
it.
Oh
here's
Scripps
Concourse,
start
credit,
Hub,
CLI,
interesting.
A
I
think
I
can
make
this
script
work
but
yeah
if,
if
I,
cancel
I'll
wait
for
you.
B
Let
me
check
oh
okay,
yes,
and
the
next
thing
would
be
the
branch
protection,
but
here
we
can
only
continue
once
we
have
the
three
Bots
in
this.
A
B
A
B
Will
see
what
comes
up
that.
B
A
A
B
You
need
a
token,
obviously
the
job
token
you
get
from
the
UAA
with
username
password
that
says
password
Grant
flow,
but
in
order
to
do
that,
you
need
a
UAA
client,
so
the
credentials
for
the
UAA.
Basically-
and
here
there
is
no
documentation
which
client
to
use,
of
course,
as
a
CF
client,
everybody
knows
that
the
cfcli
uses
it
has
no
secret.
That
has
all
the
proper
Scopes.
B
Is
it
the
CLI?
Is
it
UAA?
Is
it
the
API
or
is
it
CF
deployment
technically
I
mean
CS
API
said?
Well,
you
need
to
draw
token
I.
Don't
care
I,
hope
you
get
it
UA
says
I,
don't
care
about
the
CF
client,
it's
just
content
right,
so
we
have
we
don't
own,
it
CLI
could
own
it
or
configure
it.
It
is
actually
in
the
Manifest
of
CF
deployment.
B
So
basically,
my
my
question
is
yeah
who
owns
it
and
the
second
thing
is:
do
you
have
any
objections?
If
we
would
declare
this
client
as
API
and
document
it
somewhere,
I
mean
if
it's
there
for
years,
there's
nothing.
A
B
Well,
if
you
search
the
documentation,
obviously,
if
that's
what
is
available
to
external
users,
it's
nowhere
mentioned
it's
not
documented
and
therefore
it's
difficult
to
say
this
is
API.
That's
that's!
Basically
oil,
so
two
sentences
somewhere
in
the
documentation
would
solve
this
problem
for
us.
But
the
question
is:
is
that
okay
to
add
that
would
be
there
so
I'm
asking
around
now
and
then
I
guess:
I
will
file
a
few
PRS
to
add
that
to
the
documentation.
B
So
the
copy
team
said
we
have
no
problems
with
that
I
I
don't
see
technical
issues
at
all,
I
mean
we
should
talk
about
it
in
this
working
group
because
you
have
deployment
somehow
configures
this
client
right.
It's
it's
specified
in
the
Manifest
of
CF.
B
I
could
also
erase
this
question
on
the
CLI
slack
Channel.
If
somebody
has
objections,
I
I
would
be
surprised,
I
mean
it's.
You.
B
Right
everything
would
break
that's,
it
is
API
de
facto,
but
it's
nowhere
documented.
B
Yeah
yeah,
that's
nothing
to
do
technical
side
or
no
configuration
everything
is
there
is
in
place,
and
this
question
came
just
up
and
if,
let's
say
some
teams
in
in
companies
like
sap,
would
like
to
write
this
down
in
a.
A
B
A
A
B
I
will
then
answer
on
this
discussion
and
say:
I
talked
to
API
and
to
CF
deployments
working
group,
and
there
are
no
objections
to
document
it
and
then
I
would
propose
to
file
a
PR,
I
I,
don't
know
yet
where,
but
just
to
mention
that
this
one,
this
client
exists
in
the
stable
and
can
be
used
and
then
send
this.
B
Yeah,
so
that's
where
those
colleague
opened
it's
so
much.
You
know
you
come
to
fair
enough.
The
more
features
exists
so
why
it
is
yep
and
then
the
final
points
that
I
have
is
just
to
make.
You
aware
the
SS
open
thing
with
configuring,
CS
Linux
fs4
as
a
default
stack
this
issue
on
CF
deployment,
and
we
would
probably
start
in
the
next
weeks
too
to
make
that
happen,
because
now
the
PHP
pack
is
there.
So
all
the
prerequisites
exist
and
end
of
April
is
also
approaching
soon.
B
Okay,
so
I
guess
we
would
then
file
a
new
CF
deployment
release
I.
B
Or
whatever
a
major
release
where
we
say
from
now
on,
CF
Linux
fs4
has
integrated
into
the
main
manifest
it
is
the
default.
We
would
not
yet
remove
CF
Linux,
fs3
I
guess
we
need
to
adapt
a
little
bit
the
validation
procedure
so
that
everything
runs
on
CF,
Linux
fs4
and
this
build
pack
test
runs
then
on
CF
Linux
fs3,
so
that
until
end
of
April,
the
old
build
packs
are
also
a
little
bit
tested
so
that
we
don't.
A
B
We
will
react
experimental,
Ops
files
to
add
Steels
Linux
fs3,
because
then
we
will
remove
C
of
Linux
fs3
from
the
vanilla
installation.
That
was
the
idea.
That's
that's
another
ticket
and
that
comes
in
yeah,
beginning
of
May,
I,
would
say
or
end
of
April
I.
Leave
it
to
your
100
decide
when
okay
yeah.
A
A
Okay,
we
should
I'm
just
gonna.
Add
your
add
your
note
to
the
issue
about
adding
a
Ops
file
to
fs3
the
default
stack
again.
A
A
That
that
all
makes
sense
it's
moving
pretty
quickly,
but
we
kind
of
need
to
move
pretty
quickly,
so
I
get
it.
B
Say
it
like
this,
we
actually
move
pasta,
well,
big
landscape,
so
we
have.
We
are
now
about
already
to
switch
to
CS
Linux
for
as
a
default,
and
we
plan
to
run
a
pretty
harsh,
Force
migration
of
all
old
apps
to
the
new
stack,
with
a
risk
to
break
them.
A
B
Yeah,
of
course,
to
stop
that
at
the
last
moment
and
would
not
be
surprised
as
the
sentence,
but
that's
our
plan
to
at
the
end
of
the
day
it's
security
versus
business,
stability.
A
B
That's
right
but
yeah,
you
know
the
open
source
side.
I,
don't
see
it
because
everybody
who
has
some
serious
Landscapes,
they
have
Ops
files
to
control
this,
no
matter
what
city
points
are.
So
this
is
I.
Think
I
I
also
announced
the
TOC
that
we
are
planning
to
do
that,
because
Johan
gave
the
working
group
update
on
Tuesday,
and
here
Eric
was
listening.
B
A
Better
for
worse,
it
was
pretty
cool
that
all
the
tests
went
green
with
CF
Linux
fs4,
though
oh
yeah,
that's
that's
nice.
B
A
A
I
I'm
I
cut
a
release
of
CF
deployment,
Concourse
tasks
that
included
the
go
120
bump.
So
our
whole
pipeline
should
be
back
on,
go
120
now
or
has
has
been
now
been
moved
on
to
go
120
and
it
looks
like
things
are
working.
So
that's
good
I
think
that
theoretically,
that
would
have
broken
cats
without
the
seagull
change
and
I
was
worried
that
more
things
were
going
to
break
when
we
did
this,
but
seems
relatively
calm
so
far.
So
that's
good.
B
Was
this
is
already
in
into
pipelines,
yeah
I.
B
That's
a
good
question:
I
mean
after
end
of
April
from
May.
The
only
question
is
whether
we
want
to
keep
it
because
they
it
would
help
us
a
bionic
stem
cell
ionic
stem
cell
okay.
I
was
still
on
the
stack.
No,
that's.
B
I
would
say
we
can
kill
it.
Yeah
I
write
it
down
as
a
so
that
young
can.
A
B
A
Right
up
to
my
next
meeting,
then
good
chatting
with
you:
okay,.