Vagrant + Puppet

[boesing]

Hey there,

I cannot use your plugin in combination with vagrant.
After vagrant provision, the /etc/network/interfaces file gets totally overridden which ends up with a malformed interfaces file.
Vagrant adds some kind of wrapper around its configuration:

# VAGRANT-BEGIN
# VAGRANT-END

Well - after provisioning with puppet, the file doesnt have these comments and on the next vagrant up, vagrant creates a new section with same configuration as before. After this, the same interface is created twice and ifup wont let the interface start without an error.

Could you fix your plugin so that the comments some1 has written into that interfaces file will stay?

Thanks in advance,
Max

[adrienthebo]

Honestly? No, not really. Making this work at all would mean rewriting the parser from scratch. Granted that needs to be done for other reasons, but it's a lot of work. In addition the semantics of the interfaces file makes it very challenging to associate comments with specific statements in the file, and respecting the comment markers like what vagrant does means that the parser would have to be custom built to respect that.

[adrienthebo]

Now if someone submitted a pull request that implemented a stateful parser that could handle it and the implementation was of sufficient quality, I would totally consider merging it. However I've been fighting off RSI for months now and I'm pretty sure that rewriting this parser right here and now would ensure that I wouldn't do any coding for several months after. Yay tendons.