►
From YouTube: Dec 9, 2021 - Ortelius Architecture 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
Okay,
so
what
I
was
just
telling
ben
is
I've
been
doing
work
on
the
cloud
build
and
how
the
microservices
are
doing
their
work.
Actually,
let
me
go
over
to
a
better
branch
here.
So
one
of
the
things
when
we
do
our
cloud
build.
A
We
go
through
and
build
the
docker
images,
and
then
we
go
ahead
and
tell
the
playhob
or
slash
ortilius
that
there's
a
new
version
out
there.
So
that's
what
all
this
information
and
all
this
metadata
is-
is
telling
the
play
hub
that
we
have
a
new
version
that
we
of
this
component
and
then
the
very
last
step
after
we
grab
a
bunch
of
we
do
the
build
grab
the
digest.
A
We
go
ahead
and
and
run
a
command
that
says,
go
update
that
component
now
and
and
and
the
deploy
the
corresponding
application
to
the
environment.
So
in
this
case,
when
we
build
a
one
this,
when
you
commit-
and
you
go
through,
do
you
trigger
this
cloud?
Build
we'll
do
the
build
we'll
create
the
image
over
in
quay,
we'll
tell
the
play-up
about
it
and
then
deploy
hub
basically
goes
and
deploys
that
using
helm
over
to
our
aks
cluster.
A
Now,
when
it
does
that
one
of
the
things
that
I
enabled
was
for
that
command
that
deployment
process
to
go
ahead
and
then
update
the
values
file
with
everything
that
just
happened,
so
we
kind
of
have
like
a
point
in
time
of
all
the
the
parameters,
everything
that
was
used
for
the
deployment
process.
A
So
this
is
all
the
gory
details
that
deploy
hub
knows
about
what's
going
on
with
the
the
service
or
that
that
image
so
this
this
info,
I
had
to
do
some
playing
around
with
some
of
the
triggers
to
only
so
like
in
the
cloud
build
one
to
prevent
myself
from
going
in
an
infinite
loop.
A
I
had
to
do
some
weird
things
where,
oh,
you
can't
see
it
here.
It's
on
the
the
council
side,
where
I
had
to
say
only
run
this
cloud,
build
if
anything,
but
the
values
that
the
charts
are
getting
updated,
yeah
yeah,
so
I
don't
get
in.
B
A
Yeah
I
get
into
this
circular
loop
and
then
on
the
github
side,
with
your
action
I
actually
had
to
update
it.
To
only
do
it
when
we're
updating
the
chart
itself,
yeah
so
kind
of
the
process
flow.
Is
you
check
in
we
build
the
play
up,
deploys
it
right
now
out
to
aks
and
then
deploy
hub
then
goes
ahead
and
updates
the
values
files
in
the
chart
directory.
A
Once
that
commits
been
done,
then
this
github
action
takes
over
and
starts
creating
the
releases
for
us
yeah.
So
it's
working
really
really
cool,
because
we
we
have
a
new
releases
coming
along
nice
that
get
built
as
part
of
that
and
though
we'll
we'll
see
them
start
stacking
up.
If
I
go
over
another
repo,
let's
see,
let
me
try
another
one.
A
So
that's
that's
kind
of
what
what's
what's
happening
with
the
the
services,
so
the
the
one
question
I
have
for
you
that
what
I'd
like
to
do
is,
I
think
it's
doable,
is
on
this
action.
A
B
Yeah,
I
was
just
going
to
mention
that
yeah,
because
our
first
step
was
just
to
do
it
as
a
cron
job
but
yeah.
Absolutely
every
action
that
we're
changing
the
charts.
Then
we
should
kick
off
the
other
action
to
index
the
helm,
jumps
yeah.
A
Yeah-
and
I
think
for
my
looking
at
this
there's
two
ways
to
do
it
from
I
could
tell
one
you
do
a
a
curl
command.
You
hit
an
endpoint
and
that'll
trigger
it
or
there's
the
github
command
line,
call
which
I
think
you
can
do
an
event
or
trigger
another
action,
another
repo,
the
the
gh
command
line,
I
think,
is
going
to
be
a
little
bit
cleaner
if
we
can
get
that
sorted
out
how
to
make
that
work.
B
A
Because
I
think
at
this
point
since
we're
in
the
action,
the
gh
command
line
will
have
access
to
the
token
so
it'll
be
able
to
do
whatever
it
needs
to
do
with
the
with
that
other
repo.
Without
us
doing
any
weird
authentication
stuff.
B
I
agree
yeah
because
if,
if
we
claim
to
be
experts
in
micro
service
sprawl
and
then
we
have
59
minutes
where
we
don't
actually
know,
if
that's
the
updated
version,
then
we're
it's
going
to
be
embarrassing.
Yeah.
A
So
that's
kind
of
what's
happening
on
and
the
github
pages.
You
know
that's
all
in
place.
Let
me
get
out
of
that
file.
A
A
Maybe
I'll
jump
over
here
so
that
goes
any
better.
So
anyways,
it's
nice,
because
the
bend
that
action
that
you've
you
found
and
and
got
working
is
working
great
to
create
the
the
artifacts
off
of
the
github
pages.
So
that's
working
perfect.
The
one
I'm
having
an
interesting
problem
with
is
the
main
is
the
monorepo
and
the
reason
being
is.
A
The
cloud
build
for
this
one
we
actually
end
up
building,
so
the
monorepo
has
three
images
that
we
need
to
build.
A
So
in
this
job
we
go
through
the
and
build
the
three
images
and
then
once
it's
built,
we
go
ahead
and
tell
deploy
hub
to
go
ahead
and
deploy
all
three
images
right
now.
The
way
I
have
the
deploy
up
kind
of
side
kind
of
wired
is,
it
is
doing
a
values
file
update
for
each
component
back
on
the
same
repo.
A
Yeah,
so
this
is
so
this
is
one
of
the
re.
You
can
see
the
build
numbers,
the
same
build
number,
so
this
built
this.
This
got
deployed
and
built
same
with
the
the
nginx
and
then
the
general.
So
these
are
like
kind
of
the
three,
so
they
all
went
within
a
couple
seconds
of
each
other
getting
added
to
as
releases.
A
A
Three
three
commits
or
three
actions.
You
know
the
this
release.
Charts
is
getting
executed
three
times,
so
you
can
see
one
two
and
three
each
for
a
different
commit
for
each
one
of
the
micro
services.
C
Or
the
javascript
or
this
is
the
health
chart,
release
the
thing.
That's
running,
it's
not
that
oh.
C
A
So
this
is
the
so
the
releaser
gets
run
three
times,
but
after
if
we
hook
it,
if
we
do
the
same
logic
as
in
the
microservice
repos,
where
we
add
on
the
the
trigger
of
the
indexer
we'd
run
the
indexer
three
times
in
a
row,
and
I
then
that's
where
I'm
not
sure
if
that's
gonna
against
the
same
repo.
B
B
B
A
Yeah,
it's
an
interesting,
you
know
with
the
with
the
microservices
ones,
those
repos
coming
and
triggering
it
makes
perfect
sense.
You
know
that,
just
when
we
have
this
mono
part
that
has
three
now
I
say
we
try
it
as
is
for
now,
and
then,
if
we
see
that
it's
a
problem,
I
can
change
the
deploy
up
side
where
I'm
wiring
in
the
the
artifact
creation-
and
I
can
do
it
once
instead
of
three
times.
B
C
B
A
B
We
we've
done
it
on
our
own
one,
but
we
thought
it's
better
for
obviously
you
to
yeah.
If
you.
A
A
B
I
think
technically,
it
only
links
your
email
and
name
though
it's
not
it's
not
related
to
your
github
permissions.
A
Okay,
so
we
are.
C
C
A
A
C
A
B
Hold
up,
let
me
just
quick:
let
me
just
quickly
see
that
to
confirm
that's
correct,
so.
A
B
A
C
A
B
B
That's
just
their
question,
look
it.
Let
me
remember,
I
can't
actually
remember.
B
B
B
C
A
C
C
A
A
C
A
A
C
A
Yeah,
that
was,
they
started
doing
that
much
later
to
add
in
the
dots
oh
come
on.
A
Yeah
yeah
and
the
the
whole
process
right
now
we're
I'm
having
the
playhub
do
the
deployment
to
the
azure
cluster
so
but
at
the
same
time
it's
creating
the
values
at
yaml
and
the
github
repos
yeah.
When
we
get
argo
and
captain
all
all
plumbed
together.
All
I
have
to
do
is
turn
off
the
deploy
hub
for
from
doing
the
update,
and
we
just
let
argo
take
over
so
we're
like
90
there
on
that
side.
A
And
then
do
you
have
your
your
json
file
for
the
action
all
set?
What
do
you
want
yeah
for
because
I
remember.
C
A
B
A
That
would
be,
that
would
be
cool
if
we
could
do
you
know
a
wild
card.
B
Yeah,
so
it
looks
like
the
next
sort
of
sprint.
We
would
be
doing
a
few
github
helper
things
which
are
very
useful.
A
Yeah
yeah
so
that'll
be
definitely.
The
next
thing
is
to
plumb
all
that
in
the
other
actions
at
the
microservice
actions
add
in
the
the
trigger
of
this
action.
A
It's
it's
five
o'clock
here
in
the
evening.
It's
just
yeah
sun
just
said:
I'm
near
a
mountain,
so
yeah,
I
don't.
B
A
To
see
the
sunset,
but
I
get
to
see
the
valley,
the
colors
change
over
the
valley,
so
it
gets
a
little
bit.
You
know
another
15
minutes
earlier
we
get
the
the
darkness
creeping
in
yeah,
okay,.
C
A
B
A
B
Yeah
his
stuff's
great
by
the
way,
but
sometimes
you
just
want
to
talk
about
actual
dev
work
that
relates
to
whatever
it
is
yeah
yeah,
perfect.
Okay,
so
we
will
create
the
github
helpers
and
then
I
will
be
teaching
ben
argo
cd.
B
We
could
also
probably
use
the
youtube
ortilius
channel
to
maybe
talk
about
artifact
hub
and
how
our
journey
through
we'll
do
quite
a
cool
talk.
If
we
wanted
to
do
that
as
well,.
A
Yeah
and
the
other
thing
we
could
probably
do
with
this
channel
is
to
have
the
action
broadcast
out
to
the
channel
that
it.
B
B
B
I'll
see
if
we
need
to
get
any
discord
keys
from
you
or
apik
or
whatever
yeah.
I
don't
know
why.
B
Okay,
I
will
run
her
off
and
then
all
right
are,
you:
are
you
breaking
over
christmas
or
we're
gonna
still
meet.
A
We're
gonna
we'll
break
for
christmas
and
we'll
we'll
pick
up
around.
I
have
to
look
at
the
calendar,
but
it'll
be
probably
that
first
week
of
january,
okay.
A
B
And
then
we
can
just
give
async
updates.
Obviously,
before
that
yeah.
B
C
B
B
This
is
cool,
we
have
to
get
the
the
logo.
A
B
We
want
to
update
our
blog
to
be.
A
Much
yes,
awesome!
So
ben.
What
do
you
think
we
have
to
do
for
like
the
readme
and
do
you
think
that's
just
that
the.
A
A
C
C
I
would
assume
so
it
should
be
part
of
this.
It's
it's
either
the
next
yellow
or
is
part
of
that
url,
where
it's
actually
pulling
all
this.
You
know
stuff
right,
I'm
gonna,
guess
the
index
yaml
actually.
A
Yeah
so
looks
like
it's
oh
yeah,
because
it's
you
said
that's
on
the
crown
job.
A
C
C
A
C
C
A
I
took
a
lucky
guess
so,
the
kind
of
way
I
did
it
was.
I
found
the
the
repo
for
yep
prometheus
and
then
I
went
over
here
and
then
it
stuck
index.aml
on
the
end
of
it.
C
A
A
Now
looks
like
it
may
be:
maintaining
oh,
it's
maintaining
versions
as
well
so
see
here.
This
is
version
14
of
alert
manager,
and
then
this
is
version
13.
C
A
Yeah,
so
we
we
may
need
that
chart
releaser
action
we
may
have
to
hack
apart
a
little
bit.
A
A
Yeah
yeah
cool
all
right
and
then,
and
probably
we
should
maintainers,
probably
is
something
that
we'll
need
to
do
as
well.
C
A
A
A
A
A
This
is
very,
very
exciting.
C
A
A
A
C
I'll
catch
up
with
you
after
the
new
year,
yes,.