Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds local-hostname to the ec2 style metadata output to allow for better consumption of metadata by cloud-init
Why is this needed
When cloud-init attempts to set the hostname using the ec2 metadata source, it uses the value of local-hostname.
How Has This Been Tested?
Ran existing test suite
How are existing users impacted? What migration steps/scripts do we need?
This should not affect existing users, other than those that are hitting issues with cloud-init not setting the hostname when using hegel as an ec2 metadata source.