=== juergh_ is now known as juergh
=== cpaelzer_ is now known as cpaelzer
[21:07] <hggdh> Q: if I move my c-i bug to private, who will have access to it? Just the c-i team, or others?
[21:44] <powersj> hggdh, if I recall if you change it to "private" the maintainers of cloud-init will have access i.e. https://launchpad.net/~cloud-init-dev
[21:45] <powersj> if you move it to private security, the Canonical security team + maintainers will see it
[21:45] <powersj> I believe that is how it works, but I'm not 100% certain
[21:48] <Odd_Bloke> That matches my understanding, with the addendum that subscribers to a bug are also granted access; I've asked for clarification from LP folks, to be sure.
[21:52] <hggdh> this matches my understanding, but I pretty much only worked on Ubuntu bugs, not with upstream; I was not sure if on upstream bugs the subscribers would also have access
[21:52] <hggdh> thank you
[21:54] <Odd_Bloke> falcojr: I'm going to ask Lucas to review too (because I'm modifying/removing code that he added for a UA use case) but your review from a cloud-init perspective on https://github.com/canonical/pycloudlib/pull/114 would be appreciated.
[22:04] <falcojr> LGTM, but I'll take a closer look tomorrow
[22:28] <Odd_Bloke> Thanks!
[23:34] <AU-S2S> Trying to launch Debian 10 on AWS EC2 via a launch template. I want to keep the user_data as simple as possible by pulling the cloud-config from a URL (Repository).
[23:34] <AU-S2S> Am I missing something or is it really as simple as:
[23:35] <AU-S2S> #cloud-config
[23:35] <AU-S2S> bootcmd:
[23:35] <AU-S2S> - #include <url>
[23:36] <AU-S2S> ??
[23:36] <AU-S2S> where the <url> links to a valid YAML