Handle the default case for ssh_authorized_keys in cloud-config #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ibuildthecloud
force-pushed
the
master
branch
from
0448c3e
to
97a59e8
Compare
If no user is defined in cloud config, ssh_authorized_keys will be assigned to the root user. Signed-off-by: Darren Shepherd <[email protected]>
ibuildthecloud
force-pushed
the
master
branch
from
97a59e8
to
5caa68e
Compare
mudler
approved these changes
Oct 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If no user is defined in cloud config, ssh_authorized_keys will be
assigned to the root user. The cloud config docs don't specifically
mention this use case, but this is the default behavior of cloud-init
that most users expect.