conf on VOC, Docker related files and code external [docker-code-remote-mode] (todo: gitlab secret for credential)

[remipichon]

conf on VOC, Docker related files and code external [docker-code-remote-repo] (TODO)

When you want to configure VOC around an existing repo with Dockerfile/docker-compose and code without renaming anything on the existing repo

image

• image.remote-repo.\<Dockerfile-name>.json => will look for a Dockerfile named Dockerfile-name in remote-repo defined in json. Dockefile-name can contain any chars

  instance

• stack-instance.remote.\<sd-name>.\<si-name>[.\<suffix>].json => repo defined at stack def level
• simple-stack-instance.remote-repo.\<dc-name>.\<si-name>.json => will look for dc-name into remote-repo defined in json. dc-name can contain any chars
• stack-definition.remote-repo.\<sd-name>.json => if defined contexts, will look for them in remote-repo

===> I would like something where you don't have to rename stuff on the repo. We should specify where to find Dockerfile or docker-compose base on full name (related to remote repo)

remote repo

• cloning the remote repo is done just before using it. It is not done when we are reading the files to not block other actions
• all repo are cloned on the same /tmp folder, if several resource needs the same repo, it will be cloned only once but most likely walked for each resource

in json

• repo
  • url: valid ssh git url or public HTTP (user:pwd not supported)
  • credential: ENV pointing to Gitlab secret having the private key to clone repo ==> doc is easy http://docs.gitlab.com/ce/ci/variables/README.html#secret-variables
  • path: optional, path in remote repo to find files (Dockerfile or docker-compose file), default it walk through the repo to find the Docker related files