Sorin Sbarnea
Sorin Sbarnea
I tried used two versions of what it was supposed to be config in toml file and I observed that running `doc8` failed to use the ignore. On the other...
I observed that molecule gets confused when a driver is swithced inside a scenario, like moving from `delegated` to `docker` casing confusing errors that do not give a hint about...
It would be very useful to be able define variables that are platform specific in molecule.yml which are later exposed to playbook execution. At this moment these are accesible only...
Current base configuration is fully undocumented. The page that is most likely to describe it contain nothing https://molecule.readthedocs.io/en/latest/configuration.html and neither other page of the documentation. We not only need to...
If instances are not created, executing `molecule login` should also run create instead of giving the error below: ``` $ molecule login [11:54:43] --> Validating schema /.../molecule/default/molecule.yml. Validation completed successfully....
Molecule should be able to recreate a platform when configuration was changed. Current behavior is to re-use the already created platforms even if the molecule.yml or the Dockerfile was modified....
For reasons I will not bother to mention, testinfra should be a fully typed library. I am aware that this is a big challenge but the good news is that...
`docker run -d -P --privileged philpep/testinfra:debian_stretch` failes with: ``` 12d74da67b02890be741505e3e96df26475be943bfb1f965e1b2b671f9606b24 docker: Error response from daemon: driver failed programming external connectivity on endpoint wonderful_haibt (2577ec1a033f233c76f7a3066b60ae2ed63d24662691fa115506104c2f3f45d8): (COMMAND_FAILED: '/usr/sbin/iptables -w2 -t nat -A...
See https://github.com/actions/starter-workflows/