Hi Manuranga, This is not exactly a Puppet issue, rather Vagrant provisioning we have used is not compatible with Puppet 4. So the $subject is kind of misleading :) We will look into this issue and fix in the next release, if it needs fixing. Please create a JIRA for this.
Regarding Puppet 4 compatibility, we haven't tested yet. But looking at the deprecation list [1], I don't see any blockers. Please do raise if you notice any issues with Puppet 4. [1] https://docs.puppet.com/puppet/3.8/reference/deprecated_language.html#in-puppet-40-1 Thanks. On Thu, May 26, 2016 at 9:39 PM, Manuranga Perera <[email protected]> wrote: > We are using non-environment puppet mode this is not compatible with > puppet 4 [1] > > If manifests_path and manifest_file are specified without environments, >> the old non-environment mode will be used (which will fail on Puppet 4+). >> [2] > > > Are we planing to update to be compatible with puppet 4? > > [1] https://github.com/mitchellh/vagrant/issues/5615 > [2] https://www.vagrantup.com/docs/provisioning/puppet_apply.html > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
