►
From YouTube: Nov 11, 2021 - Ortelius Architecture Meeting AUS TZ
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
B
A
So
what
we
had
been
thinking
of
doing
is
brad
had
created
this
ortiz
charts
repo.
This
would
be
the
central
hosting
repo
and
we've
got
a
bit
of
work
done
in
there.
What
I'm
doing
is
I'm
just
doing
a
a
script
that
you
pass
in
a
list
of
repo,
so
eventually,
if
this
list
of
six
repos
becomes
10
or
20,
all
you
do
is
append
an
extra
repo
name
to
to
the
list
and
it
will
just
pull
the
individual
index
ymo.
A
So
let
me
see
if
I
can
I'll
make
it
share
the
entire
screen
to.
A
A
I'm
not
sure
if
I'm
on
the
right
yeah,
so
this
it's
just
doing
a
javascript
type
thing
you
just
pass
in
the
repost
of
the
indexes:
it
indexes
it
and
it
generates
well
a
combined
index
yml.
So
we
could
run
this
on
a
script
that
I
don't
know.
Does
it
ideally
best
case
scenario?
Is
whenever
any
of
those
repos
update,
you
would
want
to
to
pull
it.
I
haven't
gotten
to
that
part.
Yet
right
now
it's
just
we
can
set
it
on.
B
A
B
Question
so
right
now,
in
your
example,
you
have
one
tar
file
out
there.
Now
we
go
and
do
an
update.
What
happens
to
the
index.yaml
when
we
have
multiple
releases
out
in
that
microservice
repo?
Does
that
make
sense?
Do
we
have
do?
We
have
more
entries
in
the.
B
Well,
yeah,
so
like
right
here
you
have
yeah
exactly
you
have
four
releases.
Let's
say
well
just
go
up
to
your
your
main
one.
So
I'll
go
back
to
the.
B
No
go
back
to
the
microservice
repo
that
you're
just
at.
B
And
see
how
you
have
releases
one
and
we
have
one
1.0
now
tomorrow
we
make
a
change
and
we
publish
and
we're
going
to
get
a
1.1
in
the
releases
list.
A
So
I
believe
what
that
would
do,
I
believe,
because
I've
not
actually
tested
that
is
that
it
would
still
have
the
same
dependency
package
cut
and
that
will
just
go
1.1
and
the
url
just
points
to
the
new
release.
So
your
old
release,
I
believe,
would
still
sit
there,
but
it
will
no
longer
be
called
by
our
artifact
hub
because
it'll
just
sit
there.
But
now
our
url
is
updated
to
011.
A
B
Well,
what
will
happen
is
if
you
look
at
what's
in
qa
versus,
what's
in
production,
production
will
have
older
charts
than
yes,
they
would
be
stable
and
qa
would
be
the
the
testing
stuff.
So
you
know
when
we
go
to
look
at
it
from
the
artifact
hub.
A
Yeah,
I
guess
one
way
that
we
could
test.
It
is
in
right
now
this
artifact
hub,
it's
being
linked
to
one
of
my
my
fourth
versions,
so
a
potential
thing
that
we
could
try
is
in
here
we'll
just
you
know,
create
an
updated
version
of
this
chart.
I
don't
know
we
increment
the
the
version
of
here
yep.
A
Exactly
so
yeah,
that's
something
that
we
could
try
dependency
package
cut,
all
right
I'll,
just
swap
over.
Do
I
want
to
do
a
dirty
update?
That's.
D
Just
to
interrupt
on
that
one,
normally,
when
you're
doing
qa
related
branches
which
are
not
yet
production
ready,
you
install
the
crbs,
etc
separately.
So
you
have
within
your
chart.
You
have
the
option
of
actually
installing
post
installation
which
git
branch
to
refer,
etc.
So
we
could
go
down
that
route
rather
than
actually
making
changes
to
the
chart
itself.
This
is
something
which
is
similar
to
what
I
did
for
argo
when
it
was
pre-release.
D
B
A
So
right
now
in
this
instance
well,
I
guess,
because
we're
just
doing
a
test
run,
I'm
just
going
to
upgrade
the
this
version
and
see
if
the
chart
releaser
does
a
separate
release
right.
A
B
A
What
we
were
thinking
about.
B
A
A
B
A
No
wrong
branch,
but
so
now
we
know
what
what
exactly
happens
it
bumps
it
up
it.
Doesn't
I
wonder
if
the
if
the
api
version
was,
I
don't
know,
because
what
we
had
done
was
we
incremented
the
version
number,
but
not
anything
else,
not
the
app
version
or
api
version.
I
I
don't
know
if
you
changed
any
of
those
things.
Would
that
create
a
separate
entry,
or
does
it
just
replace
all
together?
Well.
A
B
Oh,
that's
on
the
github
release
side.
A
A
So
I
I
had
tried
the
well
combining
yaml
files
together
and
uploading
it
up
to
the
artifact
hub,
and
so
that's
happy
that
works,
because
one
of
the
things
that
I
was
concerned
about
is
the
yaml
file.
Just
looked
a
little
different.
Okay,
that's
char
release
says
happy.
We've
got
three
releases,
so
oh
one,
two
and
let's
have
a
look
at
the
index.
Yml
again.
A
Dependency
package
cud
right,
so
it
just
replaces
it
all
together.
Now
I
don't
know
how
that
would
affect
this
when
when
it
eventually
does
do
the
check
again-
and
I
I
can't
say
that
I
think
it
just
does
it
at
the
hour.
B
A
B
Yeah
see
if
wordpress
is
an
artifact
hub.
A
A
A
A
A
A
Sorry,
this
is
tedious
charts.
A
D
A
B
B
A
So
these
are
the
github
pages
branches
of
all
your
individual
repos
or
this
charts.
What
it
does
is
it
just
goes
and
grabs
the
index
from
as
many
of
these
as
you
need.
So
eventually,
you
could
have
ortiz
other
package
and
still
do
the
same.
Github
pages
chart
release
of
workflow,
because
that
does
the
helm
index
hand
package
all
that
business
and
uploads
them
as
releases
yeah,
and
all
that
does
is
retrieves
that
index.
So
it
knows
what
the
url
to
the
releases
are
and
generate
a
combined
index
cmo
right.
A
That's
yeah
and
it's
quite
extensible
like
what
what
I
just
did
here,
the
ortiz
other
packages-
you
just
add
it
on
to
the
list
and
you
you'll
just
get
merged
so
to
complete
this
part.
All
we
do
is
in
the
script.
You
know
just
run
like
a
node
main
js.
It
generates
the
index
ymo
and
commit
that
hamilton.
The
github
pages
branch
right.
B
A
A
Yeah
I'll
I'll
be
committing
this
thing,
and
the
last
last
bit
is
what
I
was
talking
about
with
the
whole.
You
know
node
main
commit
bit
and
it
should
work.
B
Probably
the
easiest
thing
would
be
just
create
a
a
docker
file
to
run
run
it
as
an
image
because
you
from
a
like
a
github
action,
you
can
run
any
docker
image,
so
that
may
be
just
the
easy
way
to
kind
of
bundle
it
up
and
throw
it.
So
we
can
have
it
as
a
github
action,
just
a
little
little
docker
file,
and
then
we
can
put.
We
can
build
it
and
push
it
over
to
quay
and
reference
it.
That
way.
B
Cool
the
only
other
thing
that
we
may
want
to
do
on
this
is,
I
know
it's
not
a
big
deal
for
us,
but
the
list
of
repos.
Maybe
we
should
make
that
a
property
file.
A
Yeah,
I
was
thinking
it
might
whether
we've
got
some
environmental
variables
of
some
sort.
I
don't
know
probably
false
same
deal.
B
Yeah
just
think
about
it,
it's
not
a
big
deal.
I
mean
right
now,
it's
it's,
it
works
perfectly
and
all
of
us
know
how
to
go
in
and
change
an
array.
So.
B
B
Awesome
yeah,
so
what
I've
been
doing
is
on
my
side,
working
with
ortelius
and
deploy
hub
to
when
you
go
to
do
a
deployment
that
it
goes
and
creates
and
updates
the
values
files
correctly
and
gets
the
image
tags
that
were
for
that
component
in
place.
So
the
charts
themselves
have
the
right
image
tags.
You
know
to
to
install
that
helm
chart
with
so
that
I've
been
working
on
getting
that
sorted
out.
So
we'll
have
a
a
a
nice
clean
way.
B
When
you
go
through
the
ci
process,
the
ci
process
will
create
the
components
in
ortilius
and
then
from
there,
when
you
tell
ortelius
to
do
a
deployment,
we'll
actually
dump
out
the
image
tag
into
the
properties
and
check
it
in
to
the
right
repos,
you
know
push
it
to
the
right
repos
and
then
then,
after
that,
it's
a
matter
of
just
argo.
B
Okay,
just
double
checking
and
how
about
you,
brad
you've,
just
been
the
guy
pushing
the
buttons
to
say,
send
it
to
the
production.
C
Yeah
just
been
working
with
ben
yeah,
it's
going
really
well
yeah.
B
B
C
He's
doing
really
well,
she
it's,
I,
I
think,
you're
enjoying
it
a
lot
as
well.
Aren't
you
ben
yeah
for
sure
it's
good.
C
B
C
Yeah
marty
jackson
always
approves
paul
requests.
B
I
I
know
we
we
freaked
him
out
when
karum
did
the
license,
update,
which
was
20
000
files
and
mark
he's
like
what
are
you
guys
doing?
Don't
worry
about
it,
we're
just
updating
a
few
files.
A
few.
B
I
don't
I
don't,
I
don't
think
he
sleeps
either
and
he's
not
only
doing
that
for
our
project,
but
he
he's
approving
things
for
like
the
the
cdf
landscape,
the
cdf
toc.
So
he's
like
on
all
these
projects
just
sitting
here
improving
stuff
and
reviewing
it.
It's
crazy.
A
B
Yeah
yeah
all
right,
looking
good
guys,
I
like
it.
So
I
guess
next
steps
will
be
just
getting
that
cleaned
up
a
little
bit
and
if
you
could
keep
an
eye
on
how
artifact
hub
deals
with
the
multiple
chart
versions,.
A
Bugger,
it
just
says
new
chart
version,
so
it
didn't
store
the
previous
one.
Let
me
just
share
that.
So
this
is
the
dependency
package.
Crud
oh
cut,
and
it's
just
done.
Oh
one.
Oh,
it
didn't
store.
Oh
one,
oh
yeah,
right,
it's
two!
Now!
So
that's
not
a
good
thing!.
B
B
D
B
No
worries:
well,
I'm
just
going
to
poke
around
on
this
home
repo
thinking,
real
quick
and
that's
we're
going
to
wrap
up.
So
thanks
thanks
brad.
B
Oh
interesting,
so
let
me
share
my
screen.
Real
quick.
B
So
I'm
on
the.
Let
me
throw
this
in
the
chat.
A
B
Yeah
so
somehow
I'm
wondering
if
there's
a
kind
of
like
a
bug
in
that
chart,
packager
where
it
is
just
doing
a
replace
instead
of.
A
It
sounds
like
it's
doing
that
that
first
paragraph,
that
each
time
you
want
to
paragraph
where
it
just
rebuilds
the
index
from
scratch
it
without
the
merge
flag.
So
I'm
I'm
trying
to
find
where
we
can
pass
in
this
merge
flag.
So
it
doesn't
do
that.
B
Yeah
or
you
know
the
other
way
to
handle,
it
would
be
on
your
js
to
combine
everything
instead
of
wiping
out
the
previous
index.yaml.
You
read
that
in
first
and
then
do
the
combine.
A
To
take
the
old,
indexy
ammo
and
do
like
a
comparison
if,
if
a
and
equals
b,
don't
do
anything,
but
if
there's
an
increment
a
pen
rather
than
replace.
B
A
A
That
way,
each
well
the
ortiz
charts
repo,
would
then
have
your
master
record
of
every
release
ever
done,
whereas
in
the
microservices
repos
they
would
just
hold
the
very
latest
image
very
latest
chart
I
mean
all
the
releases
would
still
be
in
there.
Exactly
yaml
would
only
refer
to
one
thing.
A
Actually,
thinking
of
doing
it,
the
other
way
around,
I
like
doing
that
that
combining
thing
in
in
the
chart
release
or
action
that
way.
You
know
your
ms
dependency
package
that
it
it
should
actually
note
down
all
the
different
revisions
on
its
own,
because
that's
a
repo,
that's
hosting
the
tree
releases,
so
yeah.
B
Yeah,
so
you
have
to
see
if
the
the
chart
releaser
can
deal
with
the
merge
yeah
this
this.
This
incremental
piece.
A
Yeah
I'll
I'll
look
that
up
and
that's
it's
definitely
not
well.
It's
not
desired
action.
How
it's
wiping
it.
B
B
A
Action
yeah,
I'm
pretty
sure
it
should
be
able
to
do
something
of
that
sort,
but
yeah
I'll
find
out
all.
B
Right
cool
all
right,
awesome,
looking
great
guys,
thank
you.