gce datasource does not handle instance ssh keys
Bug #1403617 reported by
Ben Howard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Dan Watkins | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The GCE Datasource pulls the per-project SSH but does not handle the per-instance SSH keys.
The meta-data that it handles is:
url_map = [
]
It should also handle:
('public-keys', 'instance/
Related branches
lp://staging/~oddbloke/cloud-init/lp1403617
- cloud-init Commiters: Pending requested
-
Diff: 191 lines (+95/-46)2 files modifiedcloudinit/sources/DataSourceGCE.py (+50/-42)
tests/unittests/test_datasource/test_gce.py (+45/-4)
affects: | ubuntu → cloud-init (Ubuntu) |
tags: | added: cpc-current-milestone |
Changed in cloud-init: | |
assignee: | nobody → Dan Watkins (daniel-thewatkins) |
Changed in cloud-init (Ubuntu): | |
assignee: | Dan Watkins (daniel-thewatkins) → nobody |
Changed in cloud-init: | |
status: | New → Confirmed |
Changed in cloud-init: | |
status: | Confirmed → In Progress |
Changed in cloud-init: | |
importance: | Undecided → Medium |
Changed in cloud-init: | |
status: | In Progress → Fix Committed |
Changed in cloud-init: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We need to decide how we're going to handle this.
The GCE tooling (and therefore documentation) suggest that if instance-level keys are supplied, then project-level keys are disregarded. Do we want to mirror this?
I'm torn on this one. On the one hand, we already don't match the GCE docs in the way we handle project-level keys so this may be a foolish consistency. On the other hand, this is making our images even more distinct from the GCE standards which is a Bad Thing (TM).
Also, if people are relying on setting instance-level SSH keys to exclude project-level SSH keys, then not mirroring the GCE tooling might make instances unexpectedly insecure.