Issue #8417 has been updated by Abay C.
It seems to me that if no resources actually get applied in a --noop run, then no resources should be exported as well. Exported resources being stored in the db is analogous to a resource being applied. This is in principle against the semantics of a --noop run. To me, exported resources should point to the last successful application. If the catalog was never applied, but the resources exported, it creates problems. John Bollinger wrote: > Marc Fournier wrote: > > The use-case where I would have found this useful: > > > > * install a new node, configure it using puppet, but don't have it > > monitored or backuped yet (meaning some resources mustn't get exported to > > the central monitoring/backup servers) > > * have people manually do some stuff on it, such as deploy their > > application, copy data on it, etc > > * once it's ready, put it in production, meaning among other things: apply > > the resources it has exported on the central monitoring/backup servers. > > > If I did not want certain resources to be exported for certain nodes, then I > would consider that an issue to address on the master, not on the client. It > seems strange to me, and a bit dangerous, to allow clients to override the > master in the way suggested; moreover, it presents a higher exposure to human > error than I would be comfortable with. > > The use case seems to be a natural fit for environments, at least > conceptually. It could also be addressed via node facts or external data. > > In all cases the focus should be on whether the exported resource is declared > at all. That is, I would not expect or want a simulation of resource > exportation. If a declaration of an exported resource is parsed, then that > resource should be recorded in the DB, even if the client is running in > --noop mode; in that case it would thereafter be available to be collected by > any node. ---------------------------------------- Bug #8417: Exported resources is exporting to the database with --noop flag https://projects.puppetlabs.com/issues/8417#change-91037 * Author: Andrew Thompson * Status: Re-opened * Priority: Normal * Assignee: eric sorenson * Category: exported resources * Target version: * Affected Puppet version: 2.6.4 * Keywords: ntbf * Branch: ---------------------------------------- When I run puppet with the noop flag resources are being exported to the db. I would expect it to simulate the transaction with the db... This is causing things like nagios host resources being creating before the plugins get there, so I get invalid alerts. -Andrew -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
