►
From YouTube: Contact Management Project Demo and AMA
Description
Contact Management Project Demo and AMA
A
Hey
y'all
welcome
to
the
contact
management
project,
slash
needs
or
deprecation.
Ama
I
never
came
up
with
a
better
name
for
it.
That's
just
his
name,
so
to
kind
of
kick
it
off
I'm,
going
to
show
how
we
would
set
up
a
contact
management
project
using
a
fun
little
test
storage
that
I
have
made,
and
then,
after
that,
I'll
kind
of
stop
the
share
and
we'll
open
it
up
to
just
general
questions.
Comments
concerns
all
that
fun
stuff.
A
Okay,
so
to
get
started,
we
will
go
to
this
lovely
group
that
we
have
made
original
naming
CD
or
global
orgs
and
you're
going
to
create
a
new
project,
so
you
want
to
actually
do
it
from
the
template
so
create
from
template,
go
to
group
and
we
have
contact
management
project,
template
I,
know
I'm
original
on
Navy,
for
our
naming,
we're
always
going
to
use
the
org
ID
and
we
will
simply
call
it
or
except
we
spell
correctly.
That's
that's
always
important,
so
call
it
something
like
that.
That
is
perfectly
fine.
It's
private!
A
And
we're
going
to
let
it
import,
which
takes
very
little
time
and
it'll
start
us
out
with
the
contacts
MD
file
or
contact
CML,
and
it
should
set
up
a
bunch
of
settings
first
but
to
be
thorough.
We're
always
going
to
double
check
things
so
going
over
this
quickly.
We
have
the
training
dock,
which
goes
over
each
of
these
piece
by
piece,
but
project
visibility
should
be
private.
A
It's
awesome,
enable
cve,
that's
disabled,
Forks
are
disabled,
lfs
is
disabled,
cicd
is
to
save
up
lfs,
it's
not
disabled,
so
click
that
the
important
doesn't
always
import
all
the
settings.
So
if
you
see
one,
that's
not
correct,
correct
it,
cicd
is
disabled,
Registries
can
take
disabled
analytics
disabled
requirements,
disabled
security,
compliance,
Wiki,
Snippets
package
registry,
Pages,
monitor
environments,
feature
Flags,
infrastructure
releases
are
all
disabled.
A
A
A
Maintainer,
so
we're
going
to
check
that
and
allowed
to
push
should
be
maintainers.
Developers
I'm
gonna
check
that
these
two
settings
should
be
disabled.
This
auto
updates
upon
change
so
we're
good
there
and
now
we're
gonna
go
check
our
project
files,
so
contacts
MD,
it's
a
nice
little
markdown
file
that
kind
of
walks,
the
customer
through
every
little
little
Nuance
of
it
and
then
yaml.
We've
got
our
very
blank
thing
right
now.
So
the
first
thing
we
are
going
to
need
to
do
well
actually.
A
Web
hook,
first
I
feel
like
that
is
the
better
place
to
start
so
for
our
web
hook,
our
URL
we're
going
to
grab
this
thing
from
our
file.
It'll,
basically
link
it
to
the
sync
project.
We
would
replace
token
with
the
actual
token,
but
I'm
not
going
to
do
that.
Since
this
is
a
recorded
screen,
you
know
recorded.
A
A
Cool,
so
what
we
now
need
to
do
is
edit
our
contacts
file,
so
what
we
would
normally
do
is
talk
with
customer
figure
out
the
baselines
people
to
set
up
this
is
a
test
org.
So
there's
not
a
customer
to
speak
to,
but
we'll
open
the
web
ID
under
org
ID
we're
going
to
use
the
org
ID,
which
is
also
our
path
and
then
for
contacts.
We're
going
to
set
up
some
contacts,
so
we'll
do
name
paste
and
test
email.
A
A
But
if
we
go
back
to
this,
we
should
see
Okay
cool,
so
we've
got
this
set
up.
This
will
trigger
that
pipe.
The
web
hook
has
now
triggered
to
cause
a
CI
CD
Pipeline
on
the
Ops
instance
to
run,
and
that
is
going
to
grab
these
people
and
do
a
sync
some
important
things
to
note
there.
It
only
grabs
the
first
50
people,
so
you
could
add
5
million
contacts
here
it's
only
going
to
grab
the
first
15..
A
That's
because
that's
kind
of
our
limit
for
how
many
contacts
you
can
have
in
org
with
this
setup
and
the
reason
for
that
is
API
lines,
you
can
do
a
hundred
changes
in
an
API
call,
so
50
removals
50
ads.
That's
where
we
kind
of
came
up
with
the
number
50.
that
would
add
up
to
100.
So
in
the
wildest
scenario,
you're
removing
all
50
of
your
contacts
and
I
think
50
new
ones.
That's
where
this
would
kind
of
come
into
play.
Now.
A
Traditionally,
when
we
set
this
up,
we
would
take
whomever
it
is
that
is
approved
to
do
these
changes
so
like
Jason
Ed
example,
and
we
would
invite
them
to
do
that.
You
can
go
under
projects,
information
members
and
you
can
invite
members
and
you'll
paste
in
the
email.
So
you
know
Jason
example.com,.
A
And
you
don't
need
to
worry
about
that,
and
then
you
would
click
invite
I'm
not
going
to,
because
I
don't
need
gitlab
to
send
a
pointless
email
to
a
non-existent
address
that
can't
route
anybody,
but
that's
what
you
would
do
to
invite
them
with
that
done.
We
would
go
back
to
our
ticket
fire
off
our
macro,
letting
them
know
it's
going
to
tell
them
hey
it's
set
up.
Here's
you
should
have
got
an
invite.
Let
us
know
if
you
see
any
issues
or
have
any
questions.
B
B
A
Well,
it
does
take
the
ammo
file.
It
is
also
taking
the
project
ID
from
the
web
Hook,
and
the
project.
Id
is
how
it's
actually
determining
your
org's
ID.
So
you
could
do
all
of
that.
It
won't
do
anything
for
you
just
like
you
could
in
very
change
if
I
figure
out
how
to
access
the
web
hook
and
change
the
project
ID,
but
all
you're
then
doing
is
triggering
a
sync
on
someone
else's.
A
So
I
do
have
a
bunch
of
redundancies
set
up
to
prevent
you
from
being
able
to
do
that.
You
can
manipulate
it.
All
you
want,
but
in
the
result
is
either
if
you're
triggering
your
own
sync
or
you're,
just
triggering
somebody
else's
sync:
you're
not
actually
going
to
be
able
to
modify
anyone
else's
account.
A
A
Originally
I
was
going
to
do
the
name,
but
names
change
all
the
time
for
companies,
so
it
could
get
confusing
if
somebody's
like.
Well
now,
my
company
is
called
Bob's
Burgers,
not
Bob
burgers,
and
it
felt
like
just
opening
a
potential
Avenue
of
Confusion.
By
doing
that,
so
we
just
went
with
the
work
ID
for
a
place
over
there.
A
A
A
A
C
A
A
Of
submit
an
Ops
ticket
talk
to
us
we'll
make
changes
for
you.
Thank
you,
and
the
current
method
isn't
going
anywhere.
That
will
remain.
This
is
just
our
option
of
we
heard
you
want
more
users,
and
we
heard
you
want
to
maintain
it
yourself.
Here's
the
solution
that
we
have
for
you.
If
you
want
to
do
that,
but
you
can
always
roll
back
to
we'd,
prefer
just
to
ask
Ops
to
do
this.
For
us.
A
A
A
Script
has
will
try
to
read
the
email
file
or
out
because
it
can't
parse
a
yaml
file
that
has
incorrect
syntax
it'll
fail,
pipeline
Ops
will
be
notified
via
email,
and
then
we
can
open
a
ticket
to
the
customer.
Saying
hey
here's,
what
we
noticed
and
kind
of
take
it
from
there,
so
Ops
will
be
very
notified
that
something
has
gone
wrong
so
that
we
can
reach
out
to
the
customer
and
say
this
is
what
we
noticed.
Would
you
like
our
Assistance,
or
was
this
intentional?
A
But
I
did
set
the
script
to
hard
fail
on
a
failure
to
parse
the
ammo
context.
That
way
we
get
a
failed
pipeline
email
we
get
notified.
We
can
reach
out
to
the
customer
and
kind
of
go
from
there,
whether
that
be
we
reach
out
on
maybe
their
organization
project
and
open
an
issue
saying
hey.
We
noticed
this
thing.
Would
you
like
some
help,
or
maybe
we'll
open
a
ticket
not
fully
defined
as
of
yet
I?
A
B
A
Theory
you
could
go
to
the
group
and
see
a
count
of
how
many
projects
there
are
minus
I,
guess
two
technically
one
for
that
test
project,
but
that
will
be
gone
when
this
all
goes
live
and
then
one
for
the
project
that
project
template.
Sorry
I
think
the
rewarding.
We
have
the
collaboration
project
which
we
set
up
in
the
org.
We
also
add
an
org
notes,
So
in
theory.
All
of
that
would
also
be.
A
So
we
can
get
a
quick
count
via
simples
and
desk
searches
if
there
becomes
like
a
greater
need
to
track
this
down
to
a
I,
don't
know
like
hourly
basis
or
something
we
could
maybe
add
a
field
on
orgs
where
we
just
checked
box
that
says
is
using
is
not
using
whatever,
and
then
we
can
do
it
that
way
as
well.
So
we
can
use
Explorer
to
do
a
bit
more
metrics
on
that.
If
we
needed
to.
A
A
I
think
there's
also
a
tag
for
removal
for
questions
all
that
fun
stuff.
So
we
do
have
that
ability
to
further
kind
of
go
down
it
of
how
far
down
the
metrics
rabbit
hole.
Do
you
want
to
go
because
we
can
go
pretty
far
if
you
want
to
see
the
fsat
of
customers
requesting
this,
that
will
be
something
that
you
could
obtain.
B
A
We
can
technically
set
this
up
on
any
project.
The
way
this
is
set
up
is
to
be
able
to
work
with
collaboration
projects
that
already
exist
as
of
right
now.
All
of
those
will
get
escalated
to
me
because
there
is
a
lot
of
nuance
on
how
those
are
set
up.
A
lot
of
things
we
have
to
discuss
with
the
customer.
We've
seen
collaboration
projects
where
everyone
is
already
an
owner,
and
obviously
that
would
not
work
with
this
setup.
A
So
that's
something
we
need
to
discuss
with
the
customer
of
we
could
downgrade
all
of
your
people
to
developers.
Are
you,
okay,
with
that
we've
seen
a
couple
collab
projects
that
use
Simple,
CI
CD
for
notifications?
Those
would
obviously
no
longer
work.
So
a
lot
of
those
have
a
lot
of
nuance
that
we
have
to
discuss
with
the
customer
to
figure
out
what
works
best
for
them.
A
A
All
right!
Well,
if
you
do
have
any
further
questions,
we
do
have
a
feedback
issue
that
you're
more
than
welcome
to
comment
on.
You
can
also
reach
out
to
the
Ops
Channel
or
you
can
reach
out
for
like
a
coffee
chat
with
me.
If
you
want
to
discuss
it
more
in
depth,
I'm
always
deemed
to
do
that,
but
yeah
thanks
for
attending
and
I
hope.
You
found
this
educational
and
informational
addressed
any
concerns
that
you
had
all
that
fun
stuff
and
I
look
forward
to
seeing
y'all
in
the
queues.