ensure correct ordering of concat::fragments

[kBite]

Fragments that share the same order number are ordered by name.

"${chain}-${interface}-aaa"
"${chain}-${interface}-${name}"
"${chain}-${interface}-zzz"

If name starts with upper case letter they're placed outside of interface eth0 {}:

  mod comment comment 'AAA-minimal_example' proto all ACCEPT;
interface eth0 {
  mod comment comment 'aaa-minimal_example:' proto all ACCEPT;
  mod comment comment 'minimal_example' proto all ACCEPT;
}

I looked into testing for correct ordering, but didn't find a working solution.

There is (e.g.) .that_comes_before, but that's testing against before => ....

I also unsuccessfully tried testing against the content of File[/etc/ferm.d/chains/INPUT.conf] generated by concat_file.

[kBite]

@bastelfreak Do you have an idea how to test for correct ordering?

[alexjfisher]

With rspec-puppet, I don't think you can test the final file output to verify the ordering, as concat_file generates the File resource on the agent at apply time, and not as part of the normal catalog compilation process.

This module does have acceptance tests though. You should be able to test post apply file content with these if you want.