manual provisioner should carry out configuration for ssh-keys-per-user, machine-updates-authkeys
Bug #1215777 reported by
Andrew Wilkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Low
|
Unassigned |
Bug Description
From a review comment on manual provisioner:
"If/when ssh-keys-per-user, and machine-
lands, this'll make manually provisioned machines second-class citizens. I think
we should aim to minimize the observable differences between manually and
automatically provisioned machines, really."
Changed in juju-core: | |
importance: | Undecided → Low |
status: | New → Confirmed |
summary: |
- manual provisioner must carry out configuration for ssh-keys-per-user, + manual provisioner should carry out configuration for ssh-keys-per-user, machine-updates-authkeys |
Changed in juju-core: | |
status: | Confirmed → Triaged |
tags: | added: manual-provider ssh |
tags: |
added: ssh-provider removed: manual-provider ssh |
tags: |
added: manual-provider removed: ssh-provider |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
To post a comment you must log in.
I think there might be cause for making this optional. I imagine some people might want to provision agents on the target machine, but not necessarily modify their SSH configuration (for security reasons).