[09:20] <arkin> smoser: what does that mean ?
[10:30] <Odd_Bloke> arkin: If you pass an array of shell arguments, you don't have to escape things as much.
[10:30] <Odd_Bloke> arkin: Which makes reading and updating your cloud config easier in future.
[10:30] <arkin> true ok
[13:53] <smoser> arkin, http://paste.ubuntu.com/12338745/
[13:53] <smoser> that is basically how cloud-init interprets runcmd
[13:53] <smoser> theres a trick there with yaml "anchors" which can be very helpful
[13:54] <smoser> it allows you to avoid yaml interpretation easily. so you can do more complex things like: http://paste.ubuntu.com/12338768/ and keep your sanity
[13:58] <smoser> Odd_Bloke, did jerff get some package cleaning done recently ?
[13:59] <Odd_Bloke> smoser: Not that I know of, but it is an IS-managed machine so... ¯\_(ツ)_/¯
[14:00] <smoser> i dotn think it did. wethe maas merge added python3-yaml as a dep too
[14:03] <smoser> Odd_Bloke, ok. how do i get python3-yaml installed on jerff ?
[14:07] <Odd_Bloke> smoser: Yeah, I think that's the way.
[14:07] <smoser> i thought i was in another channel :)
[23:44] <elro> Hi, I’m using cloud-init to configure Ubuntu 14.04 ec2 instances. Is there a way to avoid leaving .ucf-dist files when installing packages? For instance, I have write_files configure /etc/apt/apt.conf.d/20auto-upgrades but that results in a 20auto-upgrades.ucf-dist being left around.