You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The change made in commit bd96e69 writes the hostname to the constructed cloud-init config. That's cool but unfortunately it doesn't appear to write a newline after the host value.
This means due to the strange composition behavior documented in issue #54, userdata is now being appended to the hostname and is not running correctly.
My workaround has been to tweak our userdata to contain newlines at the start. It feels a bit hacky
The text was updated successfully, but these errors were encountered:
bwarden
added a commit
to bwarden/micro-config-drive
that referenced
this issue
Jan 26, 2023
Always add a newline after printing the hostname: entry, just in case
userdata API call returns *just* the hostname.
Update the test data to just such a bare hostname.
Fixesclearlinux#59
Always add a newline after printing the hostname: entry, just in case
userdata API call returns *just* the hostname.
Update the test data to just such a bare hostname.
Fixesclearlinux#59
The change made in commit bd96e69 writes the hostname to the constructed cloud-init config. That's cool but unfortunately it doesn't appear to write a newline after the host value.
This means due to the strange composition behavior documented in issue #54, userdata is now being appended to the hostname and is not running correctly.
My workaround has been to tweak our userdata to contain newlines at the start. It feels a bit hacky
The text was updated successfully, but these errors were encountered: