ansiblepush encodes the inventory data for host and groups in yaml files (stores them in a static directory, same for all suites), then invokes ansible with a dynamic inventory script that parses them. As explained in the issue using the same dir causes conflicts.
I changed the behavior in that the yaml files are stored in a unique per kitchen suite subdirectory. The dynamic inventory script then reads the ENV var INSTANCE_NAME to know which subdir to read the yaml files from
Fixes the following issues, one commit per issue
https://github.com/ahelal/kitchen-ansiblepush/issues/69 trivial
https://github.com/ahelal/kitchen-ansiblepush/issues/68 trivial
https://github.com/ahelal/kitchen-ansiblepush/issues/70
ansiblepush encodes the inventory data for host and groups in yaml files (stores them in a static directory, same for all suites), then invokes ansible with a dynamic inventory script that parses them. As explained in the issue using the same dir causes conflicts.
I changed the behavior in that the yaml files are stored in a unique per kitchen suite subdirectory. The dynamic inventory script then reads the ENV var INSTANCE_NAME to know which subdir to read the yaml files from
https://github.com/ahelal/kitchen-ansiblepush/issues/71 trivial, but only possible because we fixed the previous issue