[10:27] <harmw> yes harlowja, just need to find me some time :)
[14:49] <smoser> matrix3000 stop asking a quesiton and then leaving!
[14:49] <smoser> i'm not awake at 2 am
[20:22] <spandhe_> smoser: I have a question regarding the review https://code.launchpad.net/~shraddha-pandhe/cloud-init/debug-module/+merge/198119
[20:22] <smoser> k
[20:22] <spandhe_> The very last point, adding argument support
[20:23] <smoser> ok
[20:25] <spandhe_> I am a newbie, and just wondering, how useful is this going to be? I added support for namespace and output file as a parameter in the config file..
[20:25] <smoser> my use case is for running it manually
[20:26] <smoser> without having to modify config files
[20:26] <smoser> you're right, you can certainly do:
[20:26] <smoser> printf "debug:\n output: /tmp/output.txt" | sudo tee /etc/cloud/cloud.cfg.d/my-config.cfg
[20:27] <smoser> then
[20:27] <smoser> cloud-init single --frequency=always --name=debug
[20:27] <smoser> cat /tmp/output.txt
[20:27] <smoser> but i'd like to be able to have someone type just
[20:27] <smoser> cloud-init-single --frequency=always --name=debug /tmp/output.txt
[20:27] <spandhe_> ok.. this way looks a bit tedious. 
[20:29] <smoser> the only real reason for the file name as input is that 'cloud-init single' output is possibly obfuscated already 
[20:29] <smoser> (by other cloud-init config files)
[20:29] <smoser> so here specifying it directly is useful
[20:30] <spandhe_> ok..  I am facing some issues with running it this way.. let me figure those out.. 
[22:24] <spandhe_> smoser: I made the changes as suggested. 
[22:24] <smoser> spandhe_, thank you.
[22:25] <smoser> i'll take a look at this tomorrow. 
[22:25] <spandhe_> sounds good. thank you!
[22:25] <harlowja> thx spandhe_ !