New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate the users ssh-authorized-keys property #5162
Deprecate the users ssh-authorized-keys property #5162
Conversation
Thank you for helping improve cloud-init! Your change looks good to me. Have you done any additional testing to ensure that this change unblocks your use case? If so, feel free to add a comment expanding on it. Additionally, can you also sign the CLA as part of this PR? |
By allowing "ssh-authorized-keys" to pass, the rest of our generated cloud-config now passes. There are two deprecations, but if I "fix" these they will break with older/other cloud-init... We did find one bug, where we were passing |
Found an old report (from 2022), of the same issue. Closes #3984 |
39b858e
to
2ee0dac
Compare
@afbjorklund , To my knowledge, that isn't a valid key on any supported version of cloud-init. Do you have an example of a cloud-config that works when Edit: nevermind, I wasn't thinking about the '-' to '_' replacement. |
There is still code in cloud-init, that replaces dashes in keys with underscores. I can get you versions, but all major distros at least EDIT: Such as |
@afbjorklund , thanks for updated info. You are correct. I filed #5187 to fix the remaining keys. The rest of the PR looks good, but for the CLA, I noticed that you signed the CLA, but haven't yet added yourself to the CLA signers file. As part of this PR, please also add your name (alphabetically) to the CLA signers file. The full details are described in the documentation. |
2ee0dac
to
a5fe268
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Assuming CI passes, I'll merge it as-is.
Bah, one more CI failure. JSON formatting: diff --git a/cloudinit/config/schemas/schema-cloud-config-v1.json b/cloudinit/config/schemas/schema-cloud-config-v1.json
index 863c0c200..94a356747 100644
--- a/cloudinit/config/schemas/schema-cloud-config-v1.json
+++ b/cloudinit/config/schemas/schema-cloud-config-v1.json
@@ -361,7 +361,7 @@
},
"minItems": 1
},
- "ssh-authorized-keys": {
+ "ssh-authorized-keys": {
"allOf": [
{
"type": "array", |
Weird, I thought I had updated that stray tab once already.... |
The previous cloud-config still works without any issues, but it doesn't pass validation - not even as deprecated. Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
a5fe268
to
dd1082a
Compare
The previous cloud-config still works without any issues, but it doesn't pass validation - not even as deprecated.
Example from https://lima-vm.io default
Currently it does not validate, therefore.
commit b27f713
Proposed Commit Message
Additional Context
Test Steps
Checklist
Merge type