[11:09] <itjamie> would https://github.com/canonical/cloud-init/pull/1808/files (draft) be an acceptable approach to solving https://bugs.launchpad.net/bugs/1994980. 
[11:09] -ubottu:#cloud-init- Pull 1808 in canonical/cloud-init "Support string replacement for nocloud seed path" [Open]
[11:09] -ubottu:#cloud-init- Launchpad bug 1994980 in cloud-init "FR for variable substitution in nocloud-net urls (eg system serial number)" [Wishlist, Triaged]
[16:37] <meena> itjamie: it's a good start, but i would generalise it… but not so far that it would be a vector for string replacement attacks :D
[16:52] <minimal> wouldn't it be better to pass sub info as url parameters? i.e. https://host/path/user-data.yaml?serial=12345
[16:52] <minimal> s/sub/such/
[22:23] <itjamie> Its going to depend hugely on peoples usecases. Some folks may have existing systems to integrate with that arnt using url params and instead might have something like http://host/path/serialnum. Shouldnt we aim to be flexible?
[22:25] <itjamie> Depending on what system they are integrating with they may not have that choice
[22:30] <itjamie> Its also why i wrote it to be very explicit, i dont want to introduce an attack vector. By being explicit with which dmi params are supported it limits risk