| === cpaelzer__ is now known as cpaelzer | ||
| chillysurfer | the merging doc (https://cloudinit.readthedocs.io/en/latest/topics/merging.html) seems to explicitly talk about merging userdata. is vendordata subject to these same principles? (default merging, ability to specify merge-types in the vendordata cloud-config, etc.)? | 16:56 |
|---|---|---|
| chillysurfer | my testing is hinting at a "no". if userdata has a runcmd(s) and vendordata has runcmd(s), then the vendordata runcmd(s) is/are not run | 16:56 |
| chillysurfer | wondering if i could specify `merge_how` in vendordata cloud-config to change this behavior though | 16:57 |
| chillysurfer | actually i think the vendordata section answers my question: "if both vendor and user have provided ‘runcmd’ then the default merge handler will cause the user’s runcmd to override the one provided by the vendor. To append to ‘runcmd’, the user could better provide multipart input with a cloud-config-jsonp part" | 16:59 |
| chillysurfer | so the end-user (supplying userdata) would have to be _very_ explicit to allow vendordata to not get overwritten | 16:59 |
| Odd_Bloke | chillysurfer: Yes, the intent is that if a user provides a key then it completely overrides the vendor's key. | 17:34 |
| Odd_Bloke | (Unless they opt-out of that behaviour, as you noted.) | 17:35 |
| chillysurfer | Odd_Bloke: ok cool thanks for the confirmation. and besides the user specifying a cloud-config-jsonp part, there is nothing vendordata could do otherwise, right? can't specify a different merge-type in vendordata? | 17:58 |
| Odd_Bloke | chillysurfer: As far as I know, the power lies entirely with the user. | 18:03 |
| Odd_Bloke | (By design. :) | 18:03 |
| chillysurfer | yep that's what the docs seem to indicate as well :) | 18:03 |
| rharper | chillysurfer: I've not explored it yet; but I wanted to see if we could have a place to set the default merge-how values; rather than a per user-data file; it's awkward to have to have a merge-how in each input file you might use | 18:08 |
| rharper | that said, I do think the need to merge vendor-data with user-data usually indicates that what's happening in vendor-data probably should be baked into the image in some other way; for example a stand-alone vendor package integrated into the image; or event a dynamic vendor config module; | 18:10 |
| chillysurfer | rharper: yep makes total sense | 19:18 |
| chillysurfer | i have a question and some findings that are way too long for irc. what's the cloud-init mailing list that i could use? | 19:19 |
| Odd_Bloke | chillysurfer: It's the mailing list attached to this Launchpad team: https://launchpad.net/~cloud-init | 19:24 |
| chillysurfer | Odd_Bloke: perfect thanks! | 19:40 |
| AnhVoMSFT | rharper : Sorry it took a while but I pushed an update to https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785 | 20:01 |
| rharper | AnhVoMSFT: no worries; thanks | 20:01 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!