WIP googlecompute: Use "ssh-keys" metadata rather than deprecated "sshKeys"#6445
WIP googlecompute: Use "ssh-keys" metadata rather than deprecated "sshKeys"#6445tmshn wants to merge 1 commit intohashicorp:masterfrom
Conversation
7219a4a to
9117353
Compare
|
This breaks my very simple test build... this may be too backwards-incompatible to merge. |
|
It would be great to get this in, but we need to resolve why it breaks the test. |
|
Sorry to be inactive so long. I was trying to figure out the problem, but couldn't yet. |
|
I'm going to close this for now since it doesn't seem like it's being actively worked on; if you get a chance to figure out the problem, just open a new one :) . Thanks! |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
As written in the official document, metadata key "sshKeys" is deprecated and replaced by "ssh-keys".
https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys?hl=en#project-wide
With this modification, project-wide SSH keys are now allowed, and the already-closed issue #6201 is actually fixed.