How to force test kitchen attributes to be passed as integers?

Asked Jun 16 '16 at 22:17

Active Jun 16 '16 at 22:17

Viewed 308 times

I'm trying to set some attributes for some cookbooks that I imported through my kitchen.yml file.

kitchen.yml:

---
...
attributes:
    some_cookbook:
        key: 1

The cookbook that I'm importing seems to require that the attribute node['some_cookbook']['key'] be an integer. I went onto my virtual machine to look at the dna.json file that gets generated and I can see the following:

dna.json:

{
    "some_cookbook": {
        "key": "1"
    }
    "run_list": ["recipe[some_cookbook::default]"]
}

So, what I'm seeing here is that test kitchen does not preserve the type as an integer when creating the file above. If I change the file above and remove the quotes surrounding the value 1, then the recipe runs fine. Is there anything I can do to make kitchen pass in the right type? Or, perhaps this is better resolved by the cookbook maintainer validating the attributes better?

asked Jun 16 '16 at 22:17

Ci3

4,632
10
34
44

2

Try forcing the Yaml parser? `key: !!int 1` – coderanger Jun 17 '16 at 00:10
1

Also, it's legal to put JSON in YAML files. `attributes: { "some_cookbook": { "key": 1 }}' – Karen B Jun 17 '16 at 04:29
Both of these suggestions worked. Thank you so much! – Ci3 Jun 17 '16 at 15:47
any idea how to pass nil? – SmudgerDan Jul 19 '17 at 16:03
1

Using yaml notation like @coderanger pointed out `key: !!NilClass` – SmudgerDan Jul 20 '17 at 08:44

How to force test kitchen attributes to be passed as integers?

0 Answers0