Jira (PUP-5084) CapabilityFinder needs to use configured PuppetDB

[Eric Thompson (JIRA)]

Title: Message Title

Eric Thompson commented on PUP-5084   Re: CapabilityFinder needs to use configured PuppetDB Thomas Hallgren you can standup a deployer acceptance setup using beaker this way: PUPPET_FORK=er0ck PUPPET_BRANCH=nonesuch beaker --hosts config/nodes/centos7-64md-debian7-64a-64a-64a-64a-nodefaultrole.yaml --options config/git/options.rb --preserve-hosts --log-level verbose that will install puppet from git from that fork/branch. another option is installing pe, then just putting your changes into its puppet installation and flushing the jruby pools (or restart the server). in the git install you can modify the puppetdb module manifest to install puppetdb wherever you want: https://github.com/puppetlabs/deployer/blob/master/acceptance/setup/git/pre-suite/040_Startup_SignCerts.rb#L37-L77 you should be able to specify port using the database_port attribute for the puppetdb::server class at line 67 database_host is specified as $fqdn. you could apply that manifest on agents[0] for instance, instead of master and it should install puppetdb there. you'll have to update the deployer and puppet conf files to find puppetdb over there... Add Comment   This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.