At the root of this issue is the inability to define a global environment variable for cloud-init.
A patchwork of workarounds can be made, but as long as we can't define an environment variable that is inherited by all processes spawned by cloud-init, there will always be an issue waiting to happen.
At the root of this issue is the inability to define a global environment variable for cloud-init.
A patchwork of workarounds can be made, but as long as we can't define an environment variable that is inherited by all processes spawned by cloud-init, there will always be an issue waiting to happen.