►
From YouTube: Roadie and Ortelius Integration discussion
Description
The Ortelius team discusses integration to Backstage with the CTO of Roadie, Martina Iglesias Fernández
A
B
Backstage
so
we
are
the
cloud
version
and
backstage
you
probably
already
know,
is
this
developer
portal
originally
built
by
Spotify.
I
worked
in
Spotify
a
few
years
ago
for,
like
almost
five
years
and
the
last
year
and
a
half
I
worked
in
Spotify
in
the
team
that
was
building,
but
today
is
backstage,
but
it
was
the
internal
version
of
it.
C
Well,
great
everybody-
and
everybody
knows
me
I'm
Tracy,
so
I
reached
out
to
Martina
some
time
ago,
because
I
thought
we
should
be
talking
to
Rody
and
building
an
integration
into
roadie.
The
team
has
Martina,
the
team
has
started
an
integration,
I,
don't
know
what
we're
doing
with
it.
Brad
McCoy
out
of
he's
out
of
Australia,
I,
think
or
New
Zealand
has
been
working
on
it.
C
So
this
is
not
a
convenient
time
for
him
to
meet,
but
I
know
that
utkarsh
and
Steve
have
taken
a
look
at
it,
and
maybe
they
can
cover
what
we
are
doing.
But
what
we
would
like
to
do
is
primarily
two
things.
One
is
pull
in
comp.
What
we
call
component
information
from
backstage,
that's
what
a
developer
would
register
to
Backstage
and
then
the
second
one
would
be
to
include
the
ortilious
kind
of
data
Gathering
From,
whatever
data
that
there
is
already
in
backstage.
C
So,
for
example,
if
there's
already,
if
they're
already
doing
s-bombs
and
it's
Gathering,
it
we'd
want
to
pull
that
information
over.
So
we
can
begin
versioning
it
and
aggregating
it
up
to
the
application
Level.
So
what
we
are
focused
on
is
creating
release
candidates
in
a
decoupled
environment
at
an
A,
logical
application,
View.
C
D
We
need
to
have
one
of
the
steps,
let's
say
in
your
Jenkins
pipeline,
to
have
the
ortilius
CLI
step
added
to
that,
and
so
it
gets
run
as
part
of
that.
So
there's
like
there's
like
Tracy,
said:
there's,
there's
catalog
information
that
we
want,
but
also
we
want
to
be
able
to
do
be
automatically
inserted
into
pipelines
as
well.
So
it's
kind
of
like
two
different,
two
different
tasks
that
we
are
looking
at
on
the
integration
side.
D
Any
any
of
the
pipelines
so
when
backstage
goes
in
a
developer
registers,
their
component
or
their
service,
and
you
go
and
create
their
pipeline
whatever
in
whatever
pipeline
tool.
We
want
to
be
inserted
into
that.
So
if
it's
a
GitHub
action,
we
want
to
be
inserted
as
a
step
into
GitHub
action
at
a
certain
point.
If
it's
a
Jenkins
file,
we
want
to
be
inserted
there.
You
know
Etc,
you
know,
based
on
the
the
CI
CD
pipeline
tool,.
C
E
Okay
so
yesterday,
I
was
like
running
this
code,
so
it
looks
like
initial
integration
like
to
generating
to
generate
the
code
for
backstage
integration
for
artillerys.
It's
already
done
so,
if
you,
if
you
run
this
code
using
these
following
commands,
we'll
be
able
to,
you
know,
see
the
home
page,
which
is
arteries.backstage.com.
E
This
is
with
the
printed
and
back-end
book-
okay,
yes,
so
yeah.
For
some
reason,
the
authentication
with
GitHub
is
not
working
so
that
I
need
to
figure
it
out
why
that
is
not
working,
but
I
see
the
packaging
is
also
done.
So,
as
you
can
see,
the
GitHub
action
files
is
being
created
for
the
workflows,
so
creating
a
build
and
creating
the
chart
and
pushing
the
chart
in
on
like
Google
cloud
is
everything
is
done,
so,
even
if
you
deploy
this
chart
from
from
this
directory,
this
would
be.
A
E
E
Yeah,
so
that
we
need
to
do
whatever
code
we
have.
This
is
just
a
you
know
the
interface
right
here
we
have
the
example.
If
we
run
this
code
we
can
see
example,
but
we
need
to
you
know,
onboard
the
functionality
from
materials
and
yeah,
so
this
is
like
purely
independent
instance
of
Backstage.
That
is
only
for
40
years,
so
we
are
deploying
artillerys.backstage.com,
but
regarding
the
configuration
we
need
to
configure
this
so
that
you
know
we
can
configure
in
our
ways
right.
F
G
B
B
There
are
two
kinds
of
plugins:
there
are
plugins
in
the
back
end
and
plugins
in
the
front,
and
the
front-end
ones
are
typically
aggregators
or
of
information
from
third-party
services.
For
example,
the
CI
CD
tab
that
you
can
see
in
backstage
has
several
plugins
one
works
with
circle,
CI
and
another
one
with
GitHub
actions.
All
of
those
are
front-end
based
plugins.
D
B
G
D
B
G
G
B
I
I
think
you
don't
need
to
do
anything.
What
will
happen
is
that
someone
who
is
running
backstage
they
can
decide
how
to
build
their
own
backend
and
their
own
front-end
and
they
choose
what
planes
they
want
to
use.
So
at
some
point
they
will
want
to
use
artillos
and
they
know
there's
a
plugin
for
it,
so
they
will
have
to
code
that
into
their
livestage
app
and
backstage
backend.
G
B
E
B
This
is
what
backstage
integrators
look
at
when
they
want
to
create
when
they
want
to
include
another
plugin
from
somewhere
else,
and
then
in
this
readme
you
would
have
some
instructions
and
the
backstage
integrators
will
have
to
follow.
These
instructions
add
a
few
lines
of
code
and
they
should
get
up
and
running
with
your
plugin.
G
E
B
So
this
is
only
the
configuration
file,
so
on
one
hand,
you
need
to
include
these
npm
packets
that
you
want
to
add
a
code
of
your
lines
in
react
so
that
it
says.
Well
when
you
go
to
the
entity
page
and
you
go
to
this
tab,
then
I
want
you
to
show
or
tell
you
widgets,
and
then
you
probably
have
some
configuration.
You
probably
have
some
credentials
that
they
need
to
add
as
well
and
I
will
go
into
this
file.
E
B
Normally,
there's
a
customer
that
says
I
want
to
use
this
box,
not
planning
or
whatever,
and
then
we
follow
the
steps
that
we
saw
before
in
the
readme
and
we
got
those
changes
in
and
then
we
released
it
to
all
the
customers
when
it's
a
custom
plugin,
then
it's
different
because
that's
when
a
customer
can
create
a
plugin
that
they
keep
the
intellectual
property
for
and
we
cannot
share
between
customers.
So
that's
another
story,
but
in
general
we
just
follow
the
same
steps
and
we
included
in
Rowley
got
it.
B
A
D
D
A
B
B
E
D
D
It's
just
basic
auth
is
what
we
do
our
authentication
through,
so
they
have
a
a
user
ID
and
password,
basically
that
they
use
basic
basic
auth
on
our
side.
So
if
we
need
to
change
that
to
do
like
a
token
based
authentication,
so
on
the
backstage
side,
they
would
generate
an
API
token
that
we
give
backstage.
We
could
do
that
instead
of
using
user
ID
password.
B
I
think
the
basic
of
should
work
as
well.
There
are
two
ways
to
handle
this.
There
is
one
which
is
the
the
proxies
and
backstage
and
that's
a
package
I
want
to
say,
and
what
it
means
is
that
the
back
end
of
Backstage
can
keep
routes
where
it
says.
Whenever
there
is
a
request
to
my
backstage.com
proxy
slash.
B
Ortelius
I
will
redirect
that
to
the
artillius
host
and
I
will
add,
also
the
authentication.
So
the
backend
keeps
a
copy
of
the
secrets
and
whenever
any
user
goes
to
Backstage,
they
will
share
the
same
authentication
credentials
because
they
are
kept
in
the
back
end.
That's
one
way.
The
other
way
is
to
embed
that
into
the
backend
plugin
that
you
create.
B
G
D
Yeah,
okay,
so
what
we
may
want
to
do
is
just
to
get
started.
We
could
hard
code
an
authentication
just
to
get
started
and
get
everything
kind
of
plumbed
together
and
then
from
there
swap
out
with
a
different
authentication.
Once
we
get
the
front
end
and
back
end
in
pieces
in
place
and
then
do
the
the
proxy.
B
D
G
B
G
E
G
D
B
D
B
D
D
B
I
think
they
scored.
There
is
a
great
support
in
Discord
for
both
backstage
and
Broly,
and
so
many
of
those
I
think
should
be
should
be
good.
Okay
and
if
you
want
technical
help
like
I,
don't
code
that
much
anymore
to
be
honest,
I'm,
not
creating
a
department
anymore,
but
there
are
a
lot
of
people
that
have
created
plugins
in
both
Discord
workspaces.