Puppet-foreman 3.0.0

Development
#1

There's an incompatible, but necessary change merged now into
puppet-foreman master, so if anybody has further incompatible changes
they'd like to make in the next couple of weeks, please work on them now.

I've tagged a couple of PRs against the 3.0.0 milestone already.

··· -- Dominic Cleal Red Hat Engineering
#2

For those interested, it's renaming facts to receive_facts in

See Bug #8944: rename facts parameter in foreman puppet module - Installer - Foreman as well.

··· On Thu, Jan 15, 2015 at 09:12:43AM +0000, Dominic Cleal wrote: > There's an incompatible, but necessary change merged now into > puppet-foreman master, so if anybody has further incompatible changes > they'd like to make in the next couple of weeks, please work on them now.
#3

> There's an incompatible, but necessary change merged now into
> puppet-foreman master, so if anybody has further incompatible changes
> they'd like to make in the next couple of weeks, please work on them now.
>
> I've tagged a couple of PRs against the 3.0.0 milestone already.

Can we do the same for foreman_proxy? This will introduce an
incompatible change, and perhaps there's some other things that are
wanted for 3.x:

https://github.com/theforeman/puppet-foreman_proxy/pull/140
··· On Thu, Jan 15, 2015 at 09:12:43AM +0000, Dominic Cleal wrote:

–
Dominic Cleal
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

#4

Yep, done.

··· On 16/01/15 13:10, Stephen Benjamin wrote: > On Thu, Jan 15, 2015 at 09:12:43AM +0000, Dominic Cleal wrote: >> There's an incompatible, but necessary change merged now into >> puppet-foreman master, so if anybody has further incompatible changes >> they'd like to make in the next couple of weeks, please work on them now. >> >> I've tagged a couple of PRs against the 3.0.0 milestone already. > > Can we do the same for foreman_proxy? This will introduce an > incompatible change, and perhaps there's some other things that are > wanted for 3.x: > > https://github.com/theforeman/puppet-foreman_proxy/pull/140

–
Dominic Cleal
Red Hat Engineering