pushittoprod / groovible Goto Github PK

Update example1_in.groovy so instead of this:

playbook {
    play {
       ...
    }
}

You just have to write this:

play {
    ...
}

The current project state only tests the happy path, so it would be helpful to have some rules around cases where blocks are invoked in the wrong places.

For example, a playbook script with a top-level tasks block should throw a helpful error. Maybe even inform the user that tasks has to be inside of a play block or something.

Tests in the com.pushittoprod.groovible package are from my first pass. When separating the dsl and ansible layers, I implemented new tests to deal with any interface changes, but then ported the original tests to make sure they still passed. Now I have two sets of redundant tests that need to be pruned.

I inadvertently mixed JUnit 3 and JUnit 4 style tests due to IntelliJ's code generation. The old style tests should be migrated to JUnit 4 style.

Document the playbook script DSL and how to use it.