Test Idempotent behaviour of Role about ansible-elasticsearch

[gingerwizard]

@ESamir Do we have an official docker image we can use here?

[electrical]

This is indeed an important test, I'm only afraid that your proposed idea will give a lot of overhead maintaining wise.
If we could spend time on extending beaker then it will be much easier i think.

[gingerwizard]

@strootman maybe of interest.

[strootman]

So, the kitchen lifecycle is in order: destroy, create, converge, setup, verify, destroy.
As @gingerwizard pointed out in #57, running test with a regex expression will destroy each container before proceeding to the next test.
I would have to test this out, but here is my proposal.
You would have 2 suites; one to set up and one to test the idempotency. The setup suite would specify an driver_config.instance_name: "setup" and it would set the appropriate volumes on that named container; driver_config.volume: - [CONF_DIR].

- name: setup_suite 
  ...
  driver_config:
    instance_name: setup
    volume:
       - [CONF_DIR]
       - [ES_HOME]
       - etc

Then, the second suite would use volumes_from: setup.

You would have to run these suites together with a kitchen verify to prevent the tests from tearing the container down between each test.
I've successfully tested the overriding of driver_config at the suite level. Also, if needed, you can limit the platforms you test with in the suite as well.

Like I said, I have not tested this out. And I won't be able to get to it until after next week.
If nobody gets to it before I do, I'll report back!

[gingerwizard]

neillturner/kitchen-ansible#116

[gingerwizard]

The above is simpler and i believe will deliver what we need

[strootman]

Much simpler 👍

[gingerwizard]

This is needed prior to any further work on improving plugin #84

[gingerwizard]

Working on.

[bbaassssiiee]

Maybe use molecule to test idempotency?

[gingerwizard]

#267

[gingerwizard]

#267 closes this issue.