Page MenuHomeSoftware Heritage

Disable network profile for vagrant.
ClosedPublic

Authored by olasd on Oct 6 2020, 7:04 PM.

Details

Summary

This allows us to get rid of the vagant-specific hiera override completely.

Supersedes D4147

Test Plan

run vagrant with some changes (to be referenced)

Diff Detail

Repository
rSPSITE puppet-swh-site
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

\m/

(about what i just said in the other diff) there you go ;)

This revision is now accepted and ready to land.Oct 6 2020, 7:24 PM

WDYT to add a variable like profile::network::[activated|managed|whatever] to activate or not the network profile application ? It would avoid to introduce some vagrant specifics in the manifests

WDYT to add a variable like profile::network::[activated|managed|whatever] to activate or not the network profile application ? It would avoid to introduce some vagrant specifics in the manifests

Yeah, that would probably be more sensible. I can see how other cloud-inited platforms (like azure) may want to disable /etc/network/interfaces management too. I'll do that.

Implement this change with a new boolean variable