Maven building lambda functions.
Let's analyze the different sections of the Okteto Manifest:
The images defined in the build
section are:
maven
: usesDockerfile.maven
to build all the maven artifacts.users
: depends on the imagemaven
. The image built bybuild-maven
is passed as a build argument.Dockerfile.users
usesOKTETO_BUILD_MAVEN_IMAGE
toCOPY
the maven artifacts. It pushes directly to the artifact registry.users-acl
: depends on the imagemaven
. The image built bymaven
is passed as a build argument.Dockerfile.users-acl
usesOKTETO_BUILD_MAVEN_IMAGE
toCOPY
the maven artifacts. It pushes directly to the artifact registry.build.sls
: it's the image used for thedeploy
scripts. It installs thesls
binaries, but it also depends on the imagemaven
. This way, the deploy scripts will have access tosls
and the maven artifacts.
Official docs for build section.
It deploys the repo https://github.com/pchico83/localstack and waits for its pods to be available. All the logic to deploy localstack could live in another repo.
Official docs for dependencies section.
The deploy section uses the image OKTETO_BUILD_SLS_IMAGE
. It deploys the Kong configuration, the lambda functions, and uses OKTETO_ENV
to configure the public endpoints of the lambda functions.
Official docs for deploy section.
This is a nice to have, but it's a convenient way to show the lambda functions in the Okteto UI, with a custom endpoint, icon and `README.md`` file
Official docs for external section.