rnelson, I managed to create 2 .rb files and several Custom Facts (I
don't know the more succinct term).
It worked out awesomely! Thank you again.
On 3/2/2017 11:38 AM, warron.french wrote:
Awesome, thank you very much for your patience and tutoring me. I
really do appreciate it.
-
Awesome, thank you very much for your patience and tutoring me. I really
do appreciate it.
--
Warron French
On Wed, Mar 1, 2017 at 8:33 PM, Rob Nelson wrote:
> Yeah, a 'profile::base' that does nothing or just updates the motd if you
> want a very simple manifest woul
Yeah, a 'profile::base' that does nothing or just updates the motd if you
want a very simple manifest would do just fine.
On Wed, Mar 1, 2017 at 2:09 PM warron.french
wrote:
> Hi Rob, thanks.
>
> A single run? Runs don't need to change anything, but they do need to
> complete and send the repor
Hi Rob, thanks.
A single run? Runs don't need to change anything, but they do need to
complete and send the report? How do I accomplish that?
Are you saying an empty class would do?
--
Warron French
On Tue, Feb 28, 2017 at 10:30 PM, Rob Nelson wrote:
> If you deploy
If you deploy the custom fact, the agent would need to perform a single run
and then send the report to puppetdb. Afterward, it would be visible in the
admin console (assuming you mean PE console here) in all the usual places,
such as in the node details and filtering by fact valued.
The runs don'
Can I write a custom fact and see its value returned in the Admin Console?
Or does it only allow for the execution of Puppet Code based on
conditionals and criteria meeting expectations?
If the answer is yes to the first question, can I simply write the Custom
Fact, without necessarily making any
