[Cloud-init-dev] [Merge] ~jgrimm/cloud-init:fix_resolve_conf_example into cloud-init:master

The proposal to merge ~jgrimm/cloud-init:fix_resolve_conf_example into cloud-init:master has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~jgrimm/cloud-init/+git/cloud-init/+merge/321775 -- Your team cloud init development team is requested

[Cloud-init-dev] [Merge] ~jgrimm/cloud-init:fix_chef_example_source into cloud-init:master

The proposal to merge ~jgrimm/cloud-init:fix_chef_example_source into cloud-init:master has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~jgrimm/cloud-init/+git/cloud-init/+merge/321610 -- Your team cloud init development team is requested t

[Cloud-init-dev] [Merge] ~tagatac/cloud-init:docs into cloud-init:master

The proposal to merge ~tagatac/cloud-init:docs into cloud-init:master has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~tagatac/cloud-init/+git/cloud-init/+merge/322239 -- Your team cloud init development team is requested to review the prop

Re: [Cloud-init-dev] [Merge] ~tagatac/cloud-init:docs into cloud-init:master

I moved the file to match the directory structure of the rest of the topics. merging.rst was the only file that sourced its content from another file, and I didn't see any advantage to the modularity. Does the move break something that I'm missing? I couldn't find the dev flow for building the d

Re: [Cloud-init-dev] [Merge] ~powersj/cloud-init:pylint-fix-backslash into cloud-init:master

Diff comments: > diff --git a/cloudinit/config/cc_apt_configure.py > b/cloudinit/config/cc_apt_configure.py > index 06804e8..a1ceb7c 100644 > --- a/cloudinit/config/cc_apt_configure.py > +++ b/cloudinit/config/cc_apt_configure.py > @@ -6,7 +6,7 @@ > # > # This file is part of cloud-init. See

Re: [Cloud-init-dev] [Merge] ~powersj/cloud-init:pylint-fix-backslash into cloud-init:master

Diff comments: > diff --git a/cloudinit/config/cc_apt_configure.py > b/cloudinit/config/cc_apt_configure.py > index 06804e8..a1ceb7c 100644 > --- a/cloudinit/config/cc_apt_configure.py > +++ b/cloudinit/config/cc_apt_configure.py > @@ -6,7 +6,7 @@ > # > # This file is part of cloud-init. See

Re: [Cloud-init-dev] [Merge] ~tagatac/cloud-init:docs into cloud-init:master

Why did you move the file ? -- https://code.launchpad.net/~tagatac/cloud-init/+git/cloud-init/+merge/322239 Your team cloud init development team is requested to review the proposed merge of ~tagatac/cloud-init:docs into cloud-init:master. ___ Mailing

Re: [Cloud-init-dev] [Merge] ~powersj/cloud-init:fix-log-warn into cloud-init:master

ok so what I can do is propose a new pylintrc that excludes all the other warning numbers, except these two. And as I fix more warnings remove them from the excludes list. Something like: [MESSAGES CONTROL] # Errors & warnings only # W0223 - abstract-method # W0511 - fixme # W0612 - unused-vari

Re: [Cloud-init-dev] [Merge] ~powersj/cloud-init:fix-log-warn into cloud-init:master

so i think i'm ok with this. but how do we get to having pylint error now on these warnings? -- https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/322137 Your team cloud init development team is requested to review the proposed merge of ~powersj/cloud-init:fix-log-warn into

[Cloud-init-dev] [Merge] ~raharper/cloud-init:fix-snap-user-doc into cloud-init:master

The proposal to merge ~raharper/cloud-init:fix-snap-user-doc into cloud-init:master has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/321229 -- Your team cloud init development team is requested to

[Cloud-init-dev] [Merge] ~utlemming/cloud-init:lp-1676908-nic_selection_for_meta_data into cloud-init:master

The proposal to merge ~utlemming/cloud-init:lp-1676908-nic_selection_for_meta_data into cloud-init:master has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~utlemming/cloud-init/+git/cloud-init-1/+merge/322397 -- Your team cloud init develop

Re: [Cloud-init-dev] [Merge] ~smoser/cloud-init:bug/hacking-update-manager into cloud-init:master

Review: Approve continuous-integration PASSED: Continuous integration, rev:cd83b77dd1804f90694891470c04514aaa74d18f https://jenkins.ubuntu.com/server/job/cloud-init-ci/250/ Executed test runs: SUCCESS: https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=metal-amd64/250 SUCCESS: htt

[Cloud-init-dev] [Merge] ~jgrimm/cloud-init:fix_tiny_url into cloud-init:master

The proposal to merge ~jgrimm/cloud-init:fix_tiny_url into cloud-init:master has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~jgrimm/cloud-init/+git/cloud-init/+merge/321744 -- Your team cloud init development team is requested to review th

[Cloud-init-dev] [Merge] ~smoser/cloud-init:bug/hacking-update-manager into cloud-init:master

The proposal to merge ~smoser/cloud-init:bug/hacking-update-manager into cloud-init:master has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/322021 -- Your team cloud init development team is requeste

Re: [Cloud-init-dev] [Merge] ~utlemming/cloud-init:lp-1676908-nic_selection_for_meta_data into cloud-init:master

tiny nit Diff comments: > diff --git a/cloudinit/sources/helpers/digitalocean.py > b/cloudinit/sources/helpers/digitalocean.py > index 72f7bde..8d3d52a 100644 > --- a/cloudinit/sources/helpers/digitalocean.py > +++ b/cloudinit/sources/helpers/digitalocean.py > @@ -23,11 +23,8 @@ def assign_ipv4

[Cloud-init-dev] [Merge] ~utlemming/cloud-init:lp-1676908-nic_selection_for_meta_data into cloud-init:master

The proposal to merge ~utlemming/cloud-init:lp-1676908-nic_selection_for_meta_data into cloud-init:master has been updated. Commit Message changed to: DigitalOcean: assign IPv4ll address to lowest indexed interface. Previously the IPv4LL address for metadata discovery was assigned to the first