Ticket/2.7.x/10237

[stschulte]

If we specify array_matching => all for a property and the should value
is an empty array I would expect that puppet removes any possible is
value instead of ignoring the property entirely. Example taken from
issue #10237:

k5login {'/root/.k5login':
  principals => []
}

With this patch applied we do not ignore the principals property.
Instead we do remove any principal that is mentioned in
/root/.k5login (in my opinion the expected behaviour).

This change effects other types that use :array_matching => all
as well and is potentially dangerous if we have a default value
of [] somewhere. But that does not seem to be the case.

[jhelwig]

I would also expect the behavior to be to remove any principal mentioned, but it doesn't seem like a change that should be made in a point release. I'd be a lot more comfortable if it were changed to warn in 2.7.x and moved to the new behavior in a future version, especially since this affects all types with :array_matching => :all (including custom types written by users of Puppet).

[jhelwig]

I think that this should be targeted no sooner than master (for release in Telly). This is a very big change in behavior to how arrays are handled for properties/parameters.

I'm closing this so it can be re-targeted at master.