►
Description
Fleshing out the beginnings of the sub-epic "Geo: Implement frontend for Self-Service Framework replicables": https://gitlab.com/groups/gitlab-org/-/epics/2525
A
B
A
B
A
C
B
A
A
A
A
A
A
C
C
A
C
A
C
Because
my
main
concern
from
the
UI
is
trying
to
have
a
way
you
know
the
UID.
The
UI
will
be
written
kind
of
in
a
general
fashion,
just
like
our
API
is
to
where
the
UI
needs
to
have
a
way
to
kind
of
know
what
it
can
go
get
and
what
it
needs
to
display,
and
so
the
other
idea
was
to
have
like
to
say
Phi
like
a
constant
file
that
we
keep
updated.
It's
part
of
adding
new
data
types
for
that's
just
one
more
step.
C
D
A
A
A
C
Doing
that
yeah
and
I'm,
just
thinking
like
I,
think
that
creating
yeah,
just
like
the
initial
get
that
does
give
you
the
list
of
the
blobs,
like
that's
a
good
starting
issue.
Okay,
because
from
that
point,
I
could
even
hook
that
up
simply
behind
a
future
flag
in
the
UI.
To
this
we
started
working
on
a
view
to
represent
this.
C
For
instance,
I
could
at
least
using
the
blobby
API
create
a
set
of
tabs
about,
what's
were
being
returned
from
the
blob
API
and
the
repository
API,
and
then
for
me
from
there,
like
those
tabs
essentially
would
set,
would
set
the
state
to
then
use
the
the
next
level
of
API
that
we'll
make
to
actually
do
the
actions
like
getting
the
registry
and
then
all
that
stuff
that
make
sense.
Yeah.
A
C
So
I'm
the
honest,
I've
never
worked
in
an
enterprise
level
with
graphs
girl,
so
I'm
I'm
totally
open
to
learning
it.
If
you
know
if
there
are
benefi,
if
it
makes
sense,
they
go
from
a
graphical
standpoint,
I
know
of
something
you
know,
I
know
a
little
bit
of
it,
but
I'm
B
I
haven't
worked
too
much
with
it.
Yeah.
D
B
B
C
A
Api-Based
api's
stuff
should
actually
be
graphic.
Ul.
E
It's
something
similar
to
Tom,
I
I
think
there
is
like
no
golden
rule
that
it
has
to
be
graph
QL,
but
I
think
the
the
the
the
idea
is
that
if
it
makes
sense
make
it
also
available,
as
graphical
I
believe,
like
the
the
biggest
selling
point
for
graph
KL
is
that
you
can
enjoy
beautiful
things
in
the
same
request
as
you
will
do
with
database
query.
But
if
it's
something
that
you
will
not
benefit
from
doing
that,
I
don't
know.
C
A
E
A
A
A
A
Sorry,
that's,
okay,
so
okay,
so
this
is
like
kind
of
like
the
main
issue
that
we're
talking
about
today:
generalized
API
for
geo,
replicable
objects,
and
the
goal
today
was
to
create
some
smaller,
concrete
issues.
So
we
can
start
working
towards
the
world
where
we
have
self
service
framework
and
we
have
the
front
end
running
for
admins.
A
E
So
part
is
internal
consumption,
which
requires
a
special
kind
of
authorization,
actually
I
think
we
should.
We
should
probably
make
it
a
feature
that
its
internal,
these
ones,
that
we
use
to
sync
Gio,
because
this
is
not
intended
for
for
any
other
applications
to
piggyback.
On
that
like
to
retrieve
blood,
Sandra
posters,
yeah.
E
C
So
something
for
sake
of
simplicity
rest
would
be
the
way
to
go.
Just
because
that's
where
my
wheelhouse
is,
but,
as
you
know,
for
as
far
as
like
learning,
it
will
be
beneficial
to
learn
graph
and
so
I
I
could
I
could
I
can
see
both
sides
of
it?
It
did.
You
know
I'd
almost
be
more
comfortable,
maybe
like
starting
on
rest
and
working
our
way
into
graph.
But
it's
that's
a
lot.
That's
like
doubling
work,
so
I'm
not
sure
yeah.
C
My
experience
in
front
end-
and
you
know
some
of
the
api's
that
I've
worked
with
in
the
past
I've
had
a
hard
time
getting
completely
sold
on
graph.
This
is
from
a
personal,
personal,
like
usage
and
so
yeah
I
think
that's
I
think
that's
probably
like
some
of
the
contention
there,
but
I
understand
kit
loves
adopting
it
as
a
whole,
but
I
haven't
seen.
I
haven't
really
seen
anything
and
get
lab
using
graph.
E
Further
the
the
bots
and
integrations
that
we
have
I
think
there
there's
I,
know
that
internally
in
the
project,
I
think
my
requests,
Whitaker's
widgets
use
graph
QL,
but
for
integrations
there
they
will
be
very,
very
useful
because
we
we
have
to
link
a
lot
of
stuff,
like
versions
with
tags
and
groups,
users
etc.
So.
C
Yeah
so
I
asked
from
our
perspective:
do
you
I'm
not
quite
sure
what
the
data
model
looks
like,
but
is
there
a
lot
of
relational
stuff
like
that
that
will
have
to
be
making
a
mole
to
request
to
get
the
data
for,
or
is
it
as
this
more
of
when
we're
looking
at
like
a
blob
or
repositories?
Is
everything
coming
back
pretty
much
as
far.
A
A
E
C
Yeah
after
this
I
I
can
post
something
in
the
in
the
front
and
Chet.
C
E
C
C
A
C
C
A
C
Actually
nevermind
I
was
trying
to
think
about.
The
concept
of
you
know
hitting
that
when
you're
hitting
getting
the
data
based
on
the
note
drawing,
but
that
would
just
be
the
domain
so
never
mind
yes,
I
mean
assuming
that
we're
just
returning
the
string
names
like
so
am
I
had
those
things
would
be
used
as
the
parameters
for
the
next
part
of
this
blob.
You
an
API
right,
mm-hmm,
yeah,.
A
E
A
C
A
A
E
E
A
A
You
all
right
so
we've
got,
we've
got
our
thing
promoted
to
an
epic.
It
now
has
the
first
thing
an
end
point
to
list
blobs
and
our
epic
is
now
a
child
of
big
self
service.
I
think
where
to
go
at
this
one.
B
C
C
And
you
can
take
so
I
sent
the
whole
thing
you
can
take
out
like
the
constant
stuff
yeah,
but
I
think
it
I
wanted
to
show
like
that.
The
headers
right
there
and
the
bottom
of
that
that's
the
pagination
part,
so
that's
kind
of
important
okay.
So
that's
how
comes
across
and
I
there's
a
couple
of
things
in
the
designs
controller
that
sets
out
the
pagination.
C
C
Now
and
then,
if
we
also
wanted
to
allow
for
the
querying,
which
was
done
a
little
bit
higher
in
the
geo
replication
file,
the
file
you're,
looking
at
on
your
screen,
the
two
optional
params
on
line
25
and
26.
So
those
are
those
are
like
nice-to-haves
and
we
talked
about
your
concern
with
some
of
it.
I
remember.
C
The
very
least
we
could
do
sync
status
and
then
because,
and
then
we
had
talked
about,
maybe
like
a
potential
way
of
marking
things
when
you
create,
when
you
create
a
blob
model
like
marking
things
a
searchable
and
then
having
a
generic
function.
But
mm-hmm
I
don't
know
like
what
what
would
be
in
and
out
of
the
scope
of
all
what
we're
doing.
C
A
A
C
A
A
A
C
E
C
A
E
B
E
A
A
E
A
C
A
E
E
Like
repository
for
posters,
that
doesn't
make
sense,
but
for
actual,
like
images,
it
may
be
useful
for,
like
the
administrator
to
actually
see
one
of
them
if
they
are
not
sure.
If
that's
the
correct
one
you
like
able
to
actually
review
them.
C
A
E
Yeah
I
think
I
was
I
was
thinking
there,
but
any
anywhere
else.
When,
when
you
go
to
the
secondary,
you
see
like
your
notes,
and
then
you
have
like
today,
projects
and
uploads
mm-hmm
in
inside
whatever
like
package
sort
of
it
blues
or
whatever.
If
there's
like
when
you're
listening,
then
maybe
one
of
the
images
corrupts
or
something
like
that
and
you
wanna
take
a
look
love.
C
A
Currently,
people
are
asked:
okay,
there's
there's
a
an
issue
that
I
remember
where
people
are
like
asking
for
an
upload
manager
in
the
admin
area
or
on
an
issue
where
you
can
see
like
you,
you
know
what
uploads
you
added
and
delete
them,
because
there's
no
way
to
do
that.
Currently,
so
I'm
I
think.
A
A
C
I'm
thinking
about,
if
you
guys
think
it's
alright,
so
I'm
not
gonna,
be
here
tomorrow
and
I'm
about
I'm,
getting
pretty
close
to
signing
off
today
and
then
it'll
be
the
weekend.
If
it
makes
more
sense
to
me,
ask
this
question
on
Monday
yeah.
The
graphic
well
question,
if
you
guys
are
all
right
with
waiting
till
Monday
for
me
to
ask
that
yeah.
C
C
A
Yeah
alright,
well,
thank
you
Zach
and
Gabriel
and
Tom
for
joining
I
hope.
The
move
goes
smoothly.
Zach
Thanks.
C
C
Thanks
thanks
for
facilitating,
this
is
really
helpful.
No.