►
From YouTube: App Runtime Deployments Working Group [December 8, 2022]
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
Yeah,
okay
and
then
let's
get
started,
there's
not
too
much
on
the
agenda
here
he
is
hi.
Dave,
hey
everyone.
A
So
then,
let's
go
over
the
topics
we
discussed
last
time.
A
The
incompatible
routing
release
is
in
so
temporarily
changing
the
update
releases
pipeline
to
make
the
Bill
Green
was
okay,
and
it's
now
included
in
the
latest
sea
of
deployment
release,
which
is
now
a
major
release
because
of
the
breaking
change,
then
Cloud
Foundry
acceptance,
tests
for
sea
of
Linux
fs4,
so
I
enhance
the
tests
a
little
bit.
Where
is
the
pr
yeah?
So
they
now
accept
multiple
stacks
and,
in
particular,
the
build
pack
detection
tests.
A
Detect
all
configured
Stacks
here
it
is,
and
we
also
now
have
additional
tests
for
VR
build
pack
and
the
engine
X
build
packs.
So
this
gives
us
a
good
yeah
report
about
the
the
status
of
the
build
packs.
A
Okay,
build
pack
support
for
CF
Linux
fs4
I
have
opened
a
lot
of
issues
on
all
of
the
build
pack
project
projects,
so
this
is
the
latest
State.
These
five
are
supporting.
Fs4
goes
into
the
very
latest
version
and
yeah.
Everyone
else
is
now
notified
to
add
support.
A
Branch
projection
rules.
This
is.
B
C
The
next
Sprint
all
right
guys
so,
but
the
question
is
where
to
migrate.
I
think
we
have
next
week
a
session
with
Sylvester
who
set
up
a
concourse
for
the
application,
runtime
interfaces
working
group
with
a
let's
say,
more
professional
setup
and
then
yeah.
We
can
ask
questions
especially
about
the
secret
generation
and
then
maybe
directly
jump
to
this
setup.
A
D
Thing
on
this,
we
we
did
notice
I
with
cf1
case
working
group.
Just
was
upgrading
our
Concourse
and
the
latest
version
in
the
helm
chart
is
7.9
that
did
not
work
for
us.
We
ran
into
issues
with
I,
think
Guardian
on
the
workers,
and
so
we've
downgraded
back
to
7.8.3
and
that's
functional.
D
So
if
you're
looking
at
updating
the
version,
it
might
be
necessary
to
just
specify
a
Target
version,
there's
a
top
level
image
tag,
key
that
goes
into
the
helm,
values
that
you
can
specify
the
version
of
concourse
that
you
want
to
to
Target.
D
Only
difference
between
782
and
783
is
that
there
was
a
bug
with
authentication.
If
you
have
multiple
teams,
where
teams
could
send
unauthorized
requests
to
other
teams,
pipelines
or
jobs,
but
if
you've
already
got
the
one
team
like
we
do,
then
that
should
make
any
difference,
so
782
783
I,
think
are
identical
as
far
as
we're
concerned.
A
A
Okay,
good
yeah
so
see
if
deployment
there
was
another
surprising
issue
that
Dave
and
I
discussed
so
in
the
gcpe
terraform
database
provider.
A
They
sneaked
in
an
incompatible
change,
so
the
deletion
policy
was
set
to
abandon
by
default,
which
means
the
databases,
the
test
databases
for
this
one
environment
were
just
not
deleted
and
then
they
could
not
be
set
up
again,
because
the
creation
is
not
item
potent
but
but
luckily,
this
adding
this
deletion
policy
delete
on
all
the
test.
Databases
solve
the
problem.
A
I
will
still
open
an
issue
on
the
project
so
that
at
least
they
document
this
better
or
mark
it.
As
a
breaking
change.
A
A
A
Now,
what's
left
to
do,
there
are
still
a
few
infrastructure
migration
leftovers,
so
one
is
the
experimental
environment
on
AWS
here
when
I
have
time,
I
will
contact
Chris
to
and
ask
him
to
give
us
an
AWS
account
where
we
can
migrate,
and
then
we
can
also
hopefully
migrate
the
domain.
It's
it's
still
on
the
old
cf-app.com
domain
and
there
is
still
one
the
I
think
it's
this
one.
The
green
grass
environment
is
also
still
on.
A
Where
is
it
still
on
the
cf-app.com
domain
test?
Greengrass
I
think
this
is
the
one
for
stem
cell
update
tests,
so
this
one
should
also
be
migrated.
I
don't
find
the
domain
at
the
moment.
D
A
Expert
in
migrating
environments.
A
Well,
maybe
not
so.
Actually
what
we
need
is
I,
don't
know.
This
is
in
an
incredible,
basically
the
account
credentials,
and
we
call
this
Troy
and
setup
and
we'll
see.
A
A
23.3
here
we
added
steel
upper
the
the
experimental
Ops
file.
We
forgot
a
tiny
little,
a
tiny
little,
something
which
I
just
noticed
today.
A
So
there's
an
Ops
file,
use
trusted,
CA,
search
for
applications
for
fs3,
and
now
we
need
the
corresponding
ping
for
essence
or
in
experiment
yeah.
So.
C
B
A
Yet
released
that
means
for
us
at
sap.
We
have
to
temporarily
include
this
in
our
list
of
Ops
files
yeah,
but
not
a
big
thing.
If
anyone
wants
to
approve
this
pull
request,
then
I
March
it
in
and
it
comes
in
the
next
release.
A
Yeah
and
yeah,
so
we
also
will
now
integrate
the
the
new
experimental
Ops
file
and
we
will
roll
out
the
fs4
support
partial
fs4
support,
so
the
stack
will
be
available
for
everyone
and
these
five
build
packs
and
then
users
can
start
to
evaluate
and
to
migrate.
A
C
Maybe
one
question
here:
you
think
about
more
than
this
sea
of
Linux
fs4
Ops
files,
and
we
know
they
are
experimental,
but
once
well
it
was
just
working.
We
could
also
say
that
these
are
regular
Ops
files,
I
mean
eventually
they
will
go
away
because
your
Linux
fs4
will
be
the
only
Tech
but
long
term.
Who
knows
these
exercises.
B
D
C
C
D
We
can
talk
to
the
build
packs
team
and,
if
they're
happy
with
with
the
stage
of
of
fs4,
then
yes
we
can.
We
can
align
it
to
that
point.
C
And
then
the
next
step
is
then,
probably
to
you
know,
take
out
CF
Linux
fs3
right.
D
C
I
think
it's
pretty
close
and
to
yeah,
let's
say
May
April
when
the
security
updates
stopped.
Basically,
then
it's
yeah
right
time
right
at
least
yeah
I
think
so
start
to
take
the.
D
D
So
we've
got
to
work
backwards
from
there
and
decide
at
what
point
in
time
do
we
want
to
change
the
default?
I?
Guess
that's
as
soon
as
it's
considered
stable
in
all,
the
tests
are
passing.
C
C
I
asked
in
the
last
Toc
meeting
about
if
there's
a
timeline
regarding
the
remaining
build
packs,
but
there
was
only
vague
and
for
legal
reasons.
We
cannot
say
anything
so
yeah
we
have
to
wait
and
and
okay.
This
is
also
for
us
a
picture
not
so
nice,
but
that's
the
way
it
is
I
mean
yeah,
so
they
do
their
best
to
deliver
the
stuff
and
right.
D
D
C
We
have
time
to
decide
about
that.
It
also
depends
when
this
support
comes
I
mean
yeah.
Nobody
takes
CF
deployment,
as
is
in
in
any
production
environment,
so
everybody
will
do
it
right.
C
B
C
C
Of
the
remaining
applications,
and
also
the
documentation,
needs
some
attention.
I
would
say
the
easy
open
source,
Cloud
Foundry
documentation
to
from
cf2
to
CS3
and
maybe
beginning
next
year.
We
should
overhaul
the
documentation
and
say
you
know
we
provide
information
from
CF
Linux
three
to
four
search
and
replace
and
check
whether
all
the
tools
and
all
the
data
is
still
valid.
What
is
mentioned.
B
C
I
think
there
was
an
old.
What
was
it
stack,
changer
plug-in
for
cfcli
in
the
past?
Don't
know
if
that
still
works
Etc.
We
haven't
looked
at
it,
but.
D
A
C
That
that
it
shows
you,
first
of
all,
all
the
applications
that
are
still
using
a
certain
Stacks.
That
is
a
useful
tool.
I
mean
the
switching
I,
don't
know
if
that
makes
sense,
but
this
is
only
the
hardware.
Normally,
the
development
team
should
do
it
on
their
own
and
test,
of
course
up
front.
So
you
can't
do
it
as
an
operator
from
outside.
D
C
It's
well,
it's
tough,
probably
uses
V2
and
you
know
all
the
fun
stuff
but
yeah.
Let's
see.
A
Let's
see
yeah
well,
okay,
at
least
updating
the
documentation
should
be
an
option.
Custom
stack,
yeah,
yeah,
well,
okay,
it's
not
too
much
so
yeah
should
be
able
to
get
this
updated.
Okay,.
A
A
Everything
is
running.
Fine.
We
have
new
cats
release,
we
have
ionic
stem
cells
more
or
less
running,
find
the
validation
for
CF
test
helpers.
We
now
have
a
simple
pipeline
for
releasing.
B
Cool
the
other
thing
was
that
it
seems
like
there's
a
duplicate
environment
hanging
out
in
our
gcp
console,
there's
at
least
an
extra
DNS
like
Cloud
DNS
Zone
for
Bellatrix
and
I.
Haven't
it's
possible
that
there's
extra
VMS
lying
around
from
from
some
kind
of
bubble
up
for
Bellatrix
that
never
got
shut
down.
A
That
is
possible,
yes,
yeah
I'm,
not
sure
if
we
can
check
this
now.
A
You
already
mentioned
that
there
are
some
duplicate,
DNS
entries,
but
I
have
not
paid
attention
to
that.
If.
B
A
So
Bellatrix
is
used
for
for
this
bionic
validation.
So
this
is
the
Bellatrix
in
environment
and
yeah
I
mean
we
can
do
destroy
and.
A
A
I
know:
that's
really
duplicate
yeah
yeah.
This
is
a
bit
tricky
to
the
instances
to
those
have.
C
A
A
Labels
but
then
you
have
to
use
a
very
exact
Syntax
for
filtering
for
labels
or
you
get
nothing
so
I'm,
not
sure
if
we
when
I,
because
they
are
not
labeled
like
this
right.
B
B
B
Sweet
I
think
the
only
other
thing
I
wanted
to
bring
up
is
that
the
cat's
pipeline
has
been
consistently
failing
ever
since
I
merged
in
some
simple
dependabot
PRS.
So
gonna
have
to
have
a
look
at
that
at.
A
Some
point:
yeah
I,
noticed
I
just
triggered
again.
A
This
was
okay.
It's
it's
consistently
failing
on
the
push
different
path,
Wild,
Card
routes,
a
copy
of
a
packages
droplet.
It's.
A
It
looks
really
a
bit
odd
that
the
tests
of
of
completely
different
packages
are
consistently
failing.
So
okay,
no
idea,
but
but
if
you
have
time
then
please
check.
A
D
A
Not
then
I
think
we
all
have
sufficient
inputs
for
the
or
the
next
time,
so
the
last
meeting
for
this
year
would
be
on
December
22nd,
who
is
not
here?
A
Good,
so
we
meeting
will
take
place
as
planned.
Okay,
good!
That's
fine
yeah!
If
there's
nothing
more
10
I
think
we're
good
thanks
for
attending
thanks.