Puppet users - Sep 2013 - when does 'updated_at' column get updated?

Using centos 6 with puppet-2.6.17 with thin_storeconfigs with mysql and 
nagios exported resources. Every time an agent connects to the master, the 
updated_at column in the hosts table is updated. However, the updated_at 
column in the other tables is not updated even when I alter a nagios 
resource attribute like retry_check_interval. What are the conditions by 
which the updated_at column is updated for the other tables?

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Does anyone know?

On Wednesday, September 11, 2013 5:08:23 PM UTC-4, John Santana
wrote:
>
> Using centos 6 with puppet-2.6.17 with thin_storeconfigs with mysql and 
> nagios exported resources. Every time an agent connects to the master, the 
> updated_at column in the hosts table is updated. However, the updated_at 
> column in the other tables is not updated even when I alter a nagios 
> resource attribute like retry_check_interval. What are the conditions by 
> which the updated_at column is updated for the other tables?
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.