Welcome to the session on Deploying an Application with Dependencies. In this
session we're going to see how to deploy an application that has dependencies
we'll see that life time will still do its impact analysis it will then try to
understand the dependencies suggest and resolve any dependency problems and then
actually do the deployment so let's go ahead and look at this some more if
we're deploying an application with dependencies then one of the
applications is a consumer and it's being deployed to another environment
since this consumer depends on the functionality of the other application
which is a producer we need to make sure that producer applications get deployed
with the consumer applications because if we get to the target environment and
those producer applications are not there we could end up with errors life
time helps us avoid these types of situations by giving us a validate now
step where we'll be able to validate that the things we're moving from
development will have the required dependencies in the next environment so
to do all of this life time does an impact analysis it looks for any
application dependencies that do not exist or are not up-to-date in the
destination environment and in this case not up-to-date means not at the right
version number so for the deployment to proceed all of these errors would need
to be fixed so if we look through an example here we may go to our orders
application and we ask it to deploy 0.1 when it goes to deploy 0.1 to quality
what it finds is that orders is based and is using the orders base application
/ module as well so because orders is using orders base and orders base was
set to do nothing both of these are highlighted in red as being incorrect
for that particular deployment so to understand the dependencies a
little bit more once lifetime warns us of such a state where there will be
broken references and the producer application is going to be needed what
we can do is we can open the deployment that was going to be occurring and we'll
be able to see what the error is so in this case it will show us that deploying
order 0.1 results in broken references because it's not compatible with the
dublin template or the order base that's going to be in the new environment so to
understand this even better if we click on the show details when we click on the
show details it will show us all of the different modules that are being used
inside of this deployment and when we hover on the X here it gives us even
more details where the module orders requires the dublin theme from the
dublin template so we're going to be able to what we have to have the dublin
theme to be able to make this work and we also have modules orders
requiring order base from the order base application and that's because of a
number of different entities and it even shows us the number of elements that we
are reusing from these other applications so to be able to solve this
all we have to do is go look for the versions of those applications so it
mentioned the dublin template and we can grab that it mentioned order base so we
need that as well and we need to change them from do nothing to actually
deploying 0.1 and this way all three of them will be deployed together and this
will give orders all of the its dependencies and we'll fix all of the
errors that it might have now that's how we resolve dependencies when we're
actually missing different types of references we can also have a version of
the application problem so in this example we're looking at to do core and
here are to do app is going to be using the to do core and they're both at
version 1.0 so when we ask to do to be deployed we try to deploy one dot oh and
it immediately says that it can't do that and it can't do that because it
needs to do core so when we add to do core it it will go ahead and solve the
problem because both will be able to be deployed at version 1.0 but unlike
before where when we deploy to do there was no before when we were
deployment deploying things the dependency wasn't even there here that
to do core dependency is there but it's not the same version that it needs to be
to be able to work properly so in this case we go from doing nothing to
changing it over to deploying 1.0 and when both of them are set to deploy 1.0
then we can go ahead and validate that and be able to continue so when we get
to the deployment stage and we know that everything is valid the deployment can
be triggered and deploying the deploying the apps is as simple as clicking the
deployment now like we've talked about before so that's it for deploying an
application with dependencies we've shown how to solve many of the problems
when we have that and how lifetime can really help us find the right things to
make all of the dependencies become available so that's it thanks for
watching and have a great day