Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3765
** Bug watch added: github.com/canonical/cloud-init/issues #3765 https://github.com/canonical/cloud-init/issues/3765 ** Changed in: cloud-init Status: Triaged => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1889112 Title: cloud-init should support setting apply_network_config through Azure instance metadata Status in cloud-init: Expired Bug description: cloud-init currently only supports reading and setting the Azure apply_network_config option from disk (see https://cloudinit.readthedocs.io/en/latest/topics/datasources/azure.html#configuration). This means that for customers using images that have "Azure apply_network_config" set to true on disk, there is no way for customers to opt out of this behavior during VM deployment. This is because the sole location that cloud-init reads for the "Azure apply_network_config" option is from the disk. For customers that want to opt out of this behavior, the mitigation for customers would be to (1) deploy the VM, (2) ssh into the VM, (3) set the "Azure apply_network_config" option to false on disk, (4) then reboot the VM in order for the changes to take effect and prevent cloud-init from applying network config on subsequent boots. Since there is no way to opt out of this behavior on first boot, a good feature request would be for cloud-init to support reading the "Azure apply_network_config" option through cloud-configs passed in through Azure instance metadata. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1889112/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
