►
Description
5mp is now Cloud Seed ⛅🌱 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
Seven
three:
eight
nine
six
implements
the
back
end
for
the
service
account
creation.
This
was
reviewed
by
thomas
wick
and
alexander
croiter.
I
hope
I'm
pronouncing
the
names
properly.
It
has
also
been
approved
on
the
front
end,
so
natalia
has
approved
it
and
it
went
through
a
very
thorough
back-end
review
process.
So
thank
you
alex
andrew
for
that.
It
was
really
amazing
review
process
and
it's
been
approved
by
the
backend
reviewer
and
the
current
status
is
that
it's
awaiting
a
back-end
maintainer
to
review
and
approve.
A
74880
implements
the
front-end
components
for
for
the
same,
so
this
implements
basically
a
page
and
a
form
and
a
few
notifications
alerts
and
error
components
as
well.
This
is
a
waiting
front-end
review,
so
this
must
go
through
that
process.
A
The
obvious
next
step
for
me
in
the
coming
week
is
to
work
to
get
both
of
these
open
merge
requests
merged.
So
this
involves
responding
to
reviewers,
applying
some
of
the
suggestions
if
it
makes
sense
or
convincing
them
that
the
way
it's
been
implemented
is
the
right
way
to
go
through
this
process,
for
both
the
merge
requests
and
get
that
merged.
That's
the
top.
A
A
Here
are
a
few
things
we
need
to
do
to
make
sure
this
experience
of
cloud
run.
Deployments
becomes
really
smooth
for
the
end
user.
The
first
thing
is
that
it's
possible
that
the
user's
gcp
project
does
not
have
the
cloud
run.
Service
enabled
so
gitlab
must
take
the
responsibility
of
checking
the
status
for
the
service
and
enabling
it,
if
required.
A
This
should
be
seamless.
So
the
user
should
not
be
aware
that
this
is
happening.
It
must
happen
in
the
background,
in
a
sensible
way.
Second,
which
region
should
the
user
deploy
to?
He
should
have
control
over
that,
so
we
want
to
give
the
user
some
sort
of
an
interface
where
they
can
select
the
most
appropriate
region
for
their
application
and,
of
course,
finally,
there
should
be
a
sensible
interface
for
the
user
to
include
the
cloud
run
deployment
pipeline
itself.