►
From YouTube: Cloud Seed - 2022-07-29
Description
Twitter: https://twitter.com/OpenCloudSeed
Discord: https://discord.gg/sRqqdvQSd6
⛅🌱 https://hello.cloudseed.app
Cloud Seed is an open-source program lead by GitLab Incubation Engineering in collaboration with Google Cloud.
Deploying web application (and related workloads) from GitLab to major cloud providers should be trivial.
Cloud Seed makes it ridiculously simple and intuitive to consume appropriate Google Cloud services within GitLab.
A
A
Here's
the
update
for
29
july
last
week
we
spoke
about
90261
as
the
mrs
and
90034,
and
I
briefly
highlighted
about
nine
one,
six,
eight
five,
nine
one,
six
eight
five
was
a
big
merge
request
that
refactored
the
routing
across
several
endpoints
and
now
we're
doing
things
more
on
the
back
end,
with
vujs
components,
being
just
components
and
not
being
responsible
for
routing.
So
this
was
a
big
refactoring
that
has
been
merged
in
the
last
two
weeks.
That's
that's
great.
Second
one
I'll
mention
is
93174.
A
This
was
a
request.
We
got
from
one
of
our
users
in
the
private
testing
where
they
wanted
the
ordering
of
the
projects
based
on
gcp
project
ids.
So
this
affects
several
views
and
forms.
This
is
this
was
done
and
merged.
So
that's
the
mr
number
two
that
got
merged
and
happy
to
announce
that
the
production
readiness
review,
mr,
is
also
merged,
so
now
get
lab
cloud.
Seed
is
ready
to
be
rolled
out.
So
that
is
great
news
to
get
the
production
readiness
review
done
to
open.
A
Mrs
right
now,
nine
two,
three:
five:
zero
and
nine
three
five,
five,
four
nine
three
five
five
four
is
actually
a
spin-off
of
one
of
the
review
items
that
came
up
in
92350.
A
So
you
can
see
both
these,
mrs
as
just
one,
mr
and
the
idea
is
to
introduce
defensive
checks
when
setting
up
a
cloud
sql
instance.
The
way
this
works
is
that
the
instance
creation
is
an
async
process,
so
this
gets
triggered
in
the
background.
And
then
we
ask
a
worker
to
keep
monitoring
the
status
once
the
instance
is
ready
and
runnable.
A
The
worker
should
set
up
a
database,
a
user
and
and
those
kind
of
basic
things,
and
we
want
to
be
defensive
while
doing
it,
because
there
are
a
number
of
race
conditions
where
one
action
is
successful,
but
something
is
not
and
the
worker
could
go
into
a
let's
say:
a
feedback
error
loop
and
it
never
succeeds.
So
we
get
this
done
as
well.
Hopefully,
this
should
get
merged
in
the
next
two
next
few
days
and
then
the
focus
would
be
on
completing
the
whole
cycle.