When creating a new internal datagroup it was always created in the Common partition, even when providing a different partition as part of the datagroup's name.
f5_datagroup { "/integ_preview/iRule_variables":
ensure => 'present',
type => 'string',
}
In any following puppet run an api error would occur, because the datagroup was in the Common partition and not as configured in the integ_preview partition:
{"code":409,"message":"01020066:3: The requested value list (/Common/iRule_variables) already exists in partition Common.","errorStack":[],"apiError":3}
When creating a new internal datagroup it was always created in the Common partition, even when providing a different partition as part of the datagroup's name.
In any following puppet run an api error would occur, because the datagroup was in the Common partition and not as configured in the integ_preview partition: