helm) which dictates how it is configured, built, deployed etc. It can contain zero or more services, tasks and tests. It can also have build dependencies.
v-<some hash>strings scattered around logs, e.g. when building, deploying, running tests etc.
Dockerfilenext to it, as well as any number of services, tests and tasks. The module version will reflect the source code and build arguments involved, and will be visible in the image tag. The services, tasks and tests will each have separate versions because those also factor in the service configuration, test commands, environment variables and so forth.