Objects matching the expression 'resources'

• #1157 0.24.4rc3: resources inside of @@defines are not being created nor exported (defines, export, resources, virtual)
• ExportedResources Exporting and collecting resources is an extension of virtual resources_. Puppet provides an experimental superset of virtual resources, using a similar syntax. In addition to these resources being virtual, they're also "exported" to other hosts on your network. While virtual resources can only be collected by the host that specified them, exported resources can be collected by any host. You must set the storeconfigs configuration parameter to true to enable this functionality (you can see information about stored configuration on the Using Stored Configuration_ wiki page), and Puppet will automatically create a database for storing configurations (using Ruby on Rails_). This allows one host to configure another host; for instance, a host could configure its services using Puppet, and then could export Nagios configurations to monitor those services. The key syntactical difference between virtual and exported resources is that the special sigils (@ and <| |>) are doubled (@@ and <<| |>>) when referring to an exported resource. Here is an example with exported resources:: class ssh { @@sshkey { $hostname: type (collected, configuration, exported, resources, stored, virtual)
• VirtualResources By default, any resource you describe in a client's Puppet config will get sent to the client and be managed by that client. However, as of 0.20.0, resources can be specified in a way that marks them as virtual, meaning that they will not be sent to the client by default. You mark a resource as virtual by prefixing @ to the resource specification; for instance, the following code defines a virtual user:: @user { luke: ensure (exported, resources, storeconfigs, virtual)