-
Suggestion
-
Resolution: Fixed
-
None
-
None
At the moment, the login private key (of which there is one per EC2 account) is stored in the administration configuration XML file at the time it is generated.
Instead, it needs to be placed in a file in bamboo home that is suitable for use with the ssh command.
- is detailed by
-
BAM-3339 Elastic Bamboo implementation, M4
- Closed
[BAM-3298] Make SSH private key available to customer
Workflow | Original: JAC Suggestion Workflow [ 3550772 ] | New: JAC Suggestion Workflow 3 [ 3612172 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Parent |
Original:
|
|
Workflow | Original: JAC Sub-task Workflow [ 3378344 ] | New: JAC Suggestion Workflow [ 3550772 ] |
Issue Type | Original: Sub-task [ 6 ] | New: Suggestion [ 10000 ] |
Priority | Original: Medium [ 3 ] | |
Status | Original: Closed [ 6 ] | New: RESOLVED [ 5 ] |
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1440174 ] | New: JAC Sub-task Workflow [ 3378344 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1415046 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1440174 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 617195 ] | New: Bamboo Workflow 2016 v1 [ 1415046 ] |
Workflow | Original: Bamboo Workflow 2014 [ 603041 ] | New: Bamboo Workflow 2014 v2 [ 617195 ] |
Workflow | Original: Bamboo Workflow 2010 [ 203840 ] | New: Bamboo Workflow 2014 [ 603041 ] |
Assignee | Original: MarkC [ mark@atlassian.com ] | |
Issue Type | Original: Dev. Sub-task [ 13 ] | New: Sub-task [ 6 ] |
Workflow | Original: Agile Workflow with review [ 170975 ] | New: Bamboo Workflow 2010 [ 203840 ] |