►
A
We've
we've
iterated
on
that
a
little
bit
and
now
we're
sort
of
generalizing
it
in
this
approach
and
the
name
that
that
we
gave
for
this
is
just
secure
files.
That's
a
working
name
for
now
we're
looking
for
feedback
on
that,
but
essentially
this
generalizes
that
capability,
so
that
it's
not
just
focused
on
mobile,
apps
but
or
mobile
kind
of
pipelines,
but
other
type
of
pipelines
where
you
would
need
some
sort
of
binary
file
in
there.
A
So
this
could
be
code
signing
for
desktops
or
it
could
be
other
use
cases
that
we
haven't
really
defined
yet
so
by
generalizing
that
we
can
kind
of
add
that
capability
for
for
more
more
people
and
make
it
more
available.
So
the
first
issue
that
I've
linked
here
is
a
a
ux
proposal,
sort
of
a
kind
of
a
design
discussion.
This
is
kind
of
a
first
pass
at
a
design
that
I
came
up
with
and
really.
A
This
is
just
kind
of
a
very
basic
approach
where
we
allow
you
to
upload
some
files
reset
some
permissions
and
then
give
you
the
ability
to
edit
or
delete
them
and
there's
within
this
issue,
which
is
right
here,
there's
a
second
iteration
on
this
too,
where
we
can
expand
on
that
so
down
the
road.
I
would
see
this
being
being
able
to
like
expand
the
data
that
we
can
show
for
files
that
we
know
what
what
the
type
is.
A
So
if
it's
a
mobile,
if
it's
a
provisioning
profile
for
apple,
if
it's
an
android
key
store,
we
can
show
some
more
data
around
that,
because
we
know
something
about
that
file
type
for
file
types
that
we
don't
know.
We
would
kind
of
just
leave
them
as
generic,
but
I
think
this
could
add
some
nice
functionality
in
there
too.
So,
like
I
said
in
this
issue,
there
is
a
couple
mock-ups
and
looking
for
some
feedback
there.
A
So
if
you
have
any
thoughts,
please
add
them
the
second
section
here,
so
I've
got
an
architecture
discussion,
which
is
this
issue
right
here
so
kind
of
just
talking
about
how
how
we're
going
to
build
this
out
within
the
app
and
what
the
very
first
like
mvc
of
this
would
look
like
and
so
got
a
proposed
data
model,
some
api
designs
and
things
like
that.
So
getting
some
really
good
discussion
from
the
team
too.
A
So
we've
been
iterating
on
this
a
bunch
this
week
and
then
the
last
link
in
here
is
actually
just
the
first
first,
mr
that
I
made
for
this.
So
this
this
just
adds
the
the
data
model
and
then
the
the
carrier
wave
uploader
for
this.
So
you
can
see
that
here
I've
got
some
changes.
The
pipeline
isn't
passing
yet,
so
I
need
to
figure
out
what's
going
on
there,
but
we're
kind
of
getting
some
some
code
into
place
too.
A
So,
looking
for
some
feedback
on
that
as
well,
so
kind
of
the
highlights
of
this
is
like
I
said
this
is
like
a
generalized
data
model
for
supporting
binary
files.
Files
will
be
encrypted
and
uploaded
to
object,
storage
and
then
they'll
be
downloaded
by
the
runner
when
the
job
starts,
and
so
there's
going
to
be
some
other
changes
required,
not
just
within
git
lab,
but
also
within
the
workhorse
codebase
and
within
runner
as
well.
A
A
couple
considerations.
I've
also
listed
here
that
we
still
need
to
sort
of
sort
through.
Probably
some
some
limitations
would
be
good
for
this.
So
like
what's
the
maximum
file
size,
we
want
to
allow
and
are
there
certain
file,
types
that
we
want
to
restrict
this
to.
I
think
we
can
probably
start
limited
and
then
kind
of
expand
that
as
we
go,
but
we
should
have
a
plan
in
place
for
that
and
then
also
we've
also
talked
about
limiting
the
downloading
of
files
to
certain
ci
jobs.
A
So
up
next
really
just
kind
of
continuing
to
iterate
on
this,
so
I
want
to
continue
to
gather
feedback
on
the
ux
and
the
implementation
and
and
really
kind
of
get
that
that
mr
ready
for
review
so
kind
of
just
keep
pushing
on
that
and
and
then
hopefully
you
know
have
something
to
to
get
into
the
code
pretty
soon
and
and
then
start
to
to
test
it
out
so
anyway.
That's
that's!
What
we
got
for
this
week
would
love
any
feedback
that
you
have
if
you're
watching
this.