|1 anno fa|
|defaults||1 anno fa|
|meta||1 anno fa|
|molecule/default||1 anno fa|
|tasks||1 anno fa|
|templates||1 anno fa|
|.gitignore||1 anno fa|
|.yamllint||1 anno fa|
|LICENSE||1 anno fa|
|README.md||1 anno fa|
git_repository: The repository in which the dockerfile is located.
git_repository_destination: Local path in which to clone the git repository.
git_repository_extra_path: Extra path inside the cloned repo to the directory containing the Dockerfile
git_repository_tag: Version to use of the git repository.
service_name: Name of the systemd service.
service_name_prefix: Prefix to be added before the
service_namewhen creating the systemd service.
docker_registry: Domain of the registry with write access.
docker_registry_read: Domain of the registry with read access.
registry_user: User used to authenticate with the registry.
registry_password: Password used to authenticate with the registry.
docker_image: If you want to download a docker image and not a git repository
docker_image_tag: Docker tag.
docker_command: Docker command used to launch the container.
remote_build: Whether to build the docker remotely or locally [Default:
To test the role you need molecule.
And vagrant installed with libvirt
delegate_to are little fuckers to
delegate_to approach fails because it tries to ssh back with no user, so
it doesn’t matter if you copy the ssh keys there it will keep on failing.
molecule/default/playbook.yml so as to run
the playbook from there so the
local_action works. The problem is that you
have to run the playbook on a
command so you are forced to use the
changed_when: false therefore not testing the idempotence of the rol.
remote_build = False. If
anyone is interested I left my trails on this role:
default case is for
remote_build == True if you feel strong
enough to test the other case, please make a new molecule scenery. Both in this
role and in the ui-registry one.
drymer [ EN ] autistici.org lyz [ EN ] riseup.net