Re: [Dev] Puppet modules are not compatible with puppet 4

2016-06-01 Thread Imesh Gunaratne
On Thu, Jun 2, 2016 at 12:49 AM, Manuranga Perera  wrote:

> Yes it is coming when running with Vagrent, but I don't think this is
> vagrant only issue. When I try to run puppet agent apply after SSHing in I
> still get the same error. May be I can manually run by giving differing
> command line args. But for now I will downgrade to puppet 3.
>

​Yes that's better. Please create a JIRA/Github Issue with the details.

​Thanks​


> On Fri, May 27, 2016 at 12:15 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 9:39 PM, Manuranga Perera  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?
>>>
>>
>> As I see this is not a compatibility issue in Puppet modules, rather this
>> is about the Vagrant Puppet plugin which is used for testing Puppet
>> modules. We may need to test this and update the Vagrant script in the next
>> release.
>>
>> Did you see any issues in Puppet modules related to Puppet 4?
>>
>> Thanks
>>
>>>
>>> [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 : m...@wso2.com
>>>
>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.io TW: @imesh
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Puppet modules are not compatible with puppet 4

2016-06-01 Thread Manuranga Perera
Yes it is coming when running with Vagrent, but I don't think this is
vagrant only issue. When I try to run puppet agent apply after SSHing in I
still get the same error. May be I can manually run by giving differing
command line args. But for now I will downgrade to puppet 3.

On Fri, May 27, 2016 at 12:15 AM, Imesh Gunaratne  wrote:

>
>
> On Thu, May 26, 2016 at 9:39 PM, Manuranga Perera  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?
>>
>
> As I see this is not a compatibility issue in Puppet modules, rather this
> is about the Vagrant Puppet plugin which is used for testing Puppet
> modules. We may need to test this and update the Vagrant script in the next
> release.
>
> Did you see any issues in Puppet modules related to Puppet 4?
>
> Thanks
>
>>
>> [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 : m...@wso2.com
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.io TW: @imesh
> Lean . Enterprise . Middleware
>
>


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Puppet modules are not compatible with puppet 4

2016-05-26 Thread Akila Ravihansa Perera
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  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 : m...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

Blog: http://ravihansa3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Puppet modules are not compatible with puppet 4

2016-05-26 Thread Imesh Gunaratne
On Thu, May 26, 2016 at 9:39 PM, Manuranga Perera  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?
>

As I see this is not a compatibility issue in Puppet modules, rather this
is about the Vagrant Puppet plugin which is used for testing Puppet
modules. We may need to test this and update the Vagrant script in the next
release.

Did you see any issues in Puppet modules related to Puppet 4?

Thanks

>
> [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 : m...@wso2.com
>



-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.io TW: @imesh
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev