Issue #21807 has been updated by Charlie Sharpsteen.
Status changed from Unreviewed to Needs More Information
Assignee set to Nan Liu
Nan Liu wrote:
> Now puppet compares against value = { 'foo' => 1 }. This is very inconsistent
> and we end up making the in_sync? function much more complicated than
> necessary.
Are you doing the comparisons in Puppet manifests or inside a custom function?
Would it be possible to get an example of the code that this situation is
complicating? Understanding the use case will help us suggest workarounds and
design a better solution.
----------------------------------------
Bug #21807: Puppet ENC presents integer value, while manifests only present
string value
https://projects.puppetlabs.com/issues/21807#change-95215
* Author: Nan Liu
* Status: Needs More Information
* Priority: Normal
* Assignee: Nan Liu
* Category:
* Target version:
* Affected Puppet version:
* Keywords:
* Branch:
----------------------------------------
Puppet ENC can present data as integer, while puppet manifests is always
strings. This cause a comparison error.
custom_type { 'a':
value => { 'foo' => 1 },
}
Puppet manifests munges this to value = { 'foo' => '1' }, but if we use ENC
value integer 1:
custom_type { 'a':
value => { 'foo' => $enc_val }
}
Now puppet compares against value = { 'foo' => 1 }. This is very inconsistent
and we end up making the in_sync? function much more complicated than
necessary.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
