Also if you are a mcollective user it might be worth waiting a bit. Many
deprecation warnings will show on your client and server logs which are really
annoying
I made PRs to fix them so maybe next release
---
R.I.Pienaar
> On 28 Jun 2017, at 16:28, R.I.Pienaar wrote:
>
> People upgrading s
On 28/06/17 16:31, Trevor Vaughan wrote:
I'm seeing a lot of Warning: Defining "data_provider": "hiera" in
metadata.json is deprecated. How do we successfully support both Puppet
4.7 (LTS) and Puppet 5 (Today) without this garbage popping up at every run?
I don't want to kill any *real* deprec
I'm seeing a lot of Warning: Defining "data_provider": "hiera" in
metadata.json is deprecated. How do we successfully support both Puppet 4.7
(LTS) and Puppet 5 (Today) without this garbage popping up at every run?
I don't want to kill any *real* deprecation warnings, just ones that
conflict betwe
People upgrading should note the PuppetDB dependency is now postgres
postgresql96, this is not stated on the package dependency metadata so
upgrade works fine but puppetdb fails to start until you update
On Wed, Jun 28, 2017, at 15:40, Trevor Vaughan wrote:
> Awesome! We'll start working on testin
Awesome! We'll start working on testing with this as soon as we can.
First issue found: When using rspec-puppet, we need to test with
'server_facts' but now can no longer set those since they are 'reserved'
but appear to be unset by default. Any idea how to get around this?
On Tue, Jun 27, 2017 a
