Issue #11415 has been updated by Alexey Lapitsky.
Well, the problem you have is on the higher level and unrelated to this ticket. My patch fixes "to_pson_data_hash" method of the resource, and this function is called when decision about exporting the resource has already been made. konrad rzentarzewski wrote: > should we extend this bug, then? > *thin_storeconfigs* are meant for that, thus either there should be actual > filtering logic or option should conflict with *async_storeconfigs*. > what do you think? ---------------------------------------- Bug #11415: Fix for exported resources with async storeconfigs https://projects.puppetlabs.com/issues/11415#change-56968 Author: Alexey Lapitsky Status: In Topic Branch Pending Review Priority: Normal Assignee: Daniel Pittman Category: stored configuration Target version: Affected Puppet version: Keywords: exported resources, async_storecofigs Branch: https://github.com/puppetlabs/puppet/pull/276 Hey, I have a problem with the following configuration: thin_storeconfigs = true async_storeconfigs = true For example, when I tried to export nagios_host, puppetmaster lost host_name variable during pson export to stomp queue. Host_name variable is used as "namevar" for nagios_host resource and ignored during pson / json export. The patch removes "namevar" check during the export and fixes the problem. Pull request: https://github.com/puppetlabs/puppet/pull/276 -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
