Hello Scott, Thanks for your help.
Scaleway users have the possibility of changing IP adresses of their instances between reboots, so such a change would not be taken into account if the DataSourceScaleway cannot redo the network configuration at each boot. Prior to that, this was done by a systemd enabled script. It is particularly required for our IPv6 configuration that fails when done by cloud-init atm. I am not against changing our way of doing things though. My first idea was to add the network config in /etc/cloud/cloud.cfg.d which worked but only once and then got stomped by a reboot. So I am opened to suggestions. As a side node, I will prepare a second MR for the check_instance_id() method. Kind regards, ...Louis -- https://code.launchpad.net/~louis/cloud-init/+git/cloud-init/+merge/347973 Your team cloud-init commiters is requested to review the proposed merge of ~louis/cloud-init:enable_Scaleway_network_config into cloud-init:master. _______________________________________________ Mailing list: https://launchpad.net/~cloud-init-dev Post to : cloud-init-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~cloud-init-dev More help : https://help.launchpad.net/ListHelp
