At this point, you have a continuous integration pipeline that will automatically publish new Docker images for your application whenever a commit is pushed on the master branch to your source repository. At some point, you will want to deploy your Docker images to an environment (perhaps a staging environment, where you may run some end-to-end tests to verify that your application works as expected), and then to a production environment that services your end users. Although you could deploy these changes manually by updating the ApplicationImageTag input to the todobackend stack, ideally, you want to be able to continuously deploy these changes automatically into at least one environment, which provides immediate access to developers, testers, and product managers, allowing for fast feedback from the key stakeholders involved in the development of your applications.
This concept is referred to as continuous deployment. In other...