►
From YouTube: Platform SIG - Cameron Motevasselani, Armory
Description
Platform SIG - Cameron Motevasselani, Armory
The Platform SIG session at Spinnaker Summit will cover updates to the plugin framework in the last year, as well as the current state of the release process and the ongoing work in that area.
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
A
A
A
A
So
in
this
last
year,
at
the
very
end
of
2020,
we
started
adding
in
the
v2
framework,
so
there's
a
quite
a
bit
of
improvements
that
have
come
with
this
framework
and
we'll
go
over
them
a
little
bit
more
in
detail
later.
But
essentially
what
we've
done
is
we've
added
a
simpler
way
of
configuring,
your
components.
A
I
don't
want
to
get
into
too
many
technical
details,
but
we've
improved
the
way
we
can
handle
spring
plugins
so
that
you're
able
to
do
quite
a
bit
more
in
a
straight
way
again.
Spinnaker,
it's
a
very
project,
so
we
added
some
nice
quality
of
life
around
plugin
development,
we've
also
added
a
open
source,
plugin
repository
and
right
now,
every
I
think
it
was
224
and
on.
I
think
we
have
sorry
124.
A
A
A
So
a
lot
of
people's
passwords
broke
in
the
past
and
our
marine
had
created
this
observability
plugin
to
help
with
monitoring
metrics,
and
so
this
was
a
really
good
win
from
the
plug-in
framework.
Essentially,
the
community
decided
that
monitoring
should
not
be
part
of
the
platform
itself
and
because
we
have
the
plug-in
framework,
we
were
able
to
split
that
functionality
out
from
hispanic
countries
itself.
A
A
A
A
We
wanted
to
like
rip
jenkins
out
that
also
added
some
challenges
so
on
and
so
forth,
but
we
kind
of
had
a
forcing
function
this
year
with
the
end
of
life
of
contrary,
so
big
tree's
going
end
of
life
on
july
4th.
So
we
have
to
move
off
of
entry,
so
that
was
a
surprising
piece
of
news
for
us,
so
that
did
that
was
kind
of
a
forcing
function
to
get
us
to
update
the
current
release
process.
A
A
This
work
is
currently
in
progress.
So
what
we're
doing
right
now
is
we're
trying
to
keep
as
much
of
the
current
release
process
in
place
as
much
as
possible.
However,
there's
going
to
be
certain
things
that
will
change
if
you
are
a
consumer
of
spinnaker,
where
you
consume
bonds
and
retaliate
in
order
to
to
install
a
deployment.
A
A
So
these
are
the
main
two
initiatives
that
we're
working
on
with
the
platform
this
in
this
past
year
and
we're
still
working
on
that
framework
has
pretty
stable
for
a
while
now,
so
we're
not
seeing
too
much
development
on
the
framework
itself.
That
being
said,
we're
seeing
quite
a
bit
of
movement
in
the
plug-in
development
space,
so
a
lot
of
people
are
creating.
A
A
So
before
plugins
were
around
sharing
best
practices
with
the
community
was
was
talented,
so
spinnaker
has
a
lot
of
features.
However,
there's
some
things
that
are
missing.
One
of
the
great
things
about
spinnaker
is
having
best
practices
codified
within
stages,
so
we
were
thinking
when
we
started
the.
A
A
A
A
A
Targeted
finding
custom
changes,
because
that's
a
the
main
way
that
users
interact
with
spencer,
corporate
pipelines
and
stage
is
a
very
simple
concept,
for
we
got
a
lot
of
interest
in
this,
and
that
was
awesome.
It
was
also
a
little
challenging
because
adding
trust
the
class
path
is
not
necessarily
the
most
not
the
preferred
way
to
operate
systems,
there's
a
lack
of
metrics
monitoring.
A
If
your
libraries
were
out
of
sync
with
the
underlying
spinnaker
service,
it
would
cause
issues,
so
we
quickly
realized
there's
a
lot
of
interest.
We
need
to
level
up
because
of
the
the
interest
and
everything
we
created
the
platform
say,
and
that's
what
we're
talking
about
so
again
talking
about
what
was
wrong
with
them.
There
was
a
lack
of
metrics
and
the
quality
of
life
for
both
spinnaker
operators,
as
well
as
plug-in
developers
was
not
was
not
awesome.
There
was
a
lot
of
work.
A
A
A
A
A
A
It
was
version
123.
What
was
happening
was
that
you
had
a
custom
stage
and
you
restarted
your
organization
changed
the
load
order
of
plug-ins
and
how
things
were
initialized.
So
it
was
not
a
good
time
and
our
orchards
totally
failed
after
that,
so
they
were
not
processing,
messages
and
yeah.
Again
it
was.
It
was
a
bad
time,
so
we
had
we
discovered
a
few
underlying
issues
with
the
one
timer.
In
addition,
it
was
not
actually
springy
enough.
There
was
still
quite
a
bit
of
quality
of
life
equipment.
A
A
Rather,
we
reduce
the
amount
of
knowledge
that
our
operators
need
in
order
to
configure
their
plugins
in
the
v1
framework.
We
link
some
information
about
the
underlying
classes.
Configurations
spec
operators
would
have
to
know.
Oh,
these
configurations
went
with
this
underlying
class,
and
that
was
challenging.
So
we
have
it
all
under.