Feature #4421
open
GCE Compute Resource: Change Certificate Path UI element to File Upload
Description
It would be very handy if the UI for adding GCE (Google Compute Engine) projects as a compute resource on foreman was updated to use a file upload field instead of a basic text field. It would allow the user to select the certificate keyfile associated with the authorised Google client ID and upload it directly to foreman instead of having to use an alternative route to get the key onto the foreman server. Foreman would be able to decide where the keys should be kept on the server and make sure the required permissions were applied to the key file and location for security.
Possible Implications:
Additional code & settings to configure the folder location on foreman
Logic to test for required read, write permissions for foreman user
Files
Updated by Dominic Cleal almost 11 years ago
- Translation missing: en.field_release deleted (
2)
Updated by Dominic Cleal over 10 years ago
- Category changed from Compute resources to Compute resources - GCE
Updated by Dominic Cleal almost 10 years ago
When adding a new service account, the GCE console automatically gives you a little JSON file containing many of the details that are needed for setup.
It has a small hash inside containing: private_key_id, private_key (PEM encoded string), client_email, client_id and type (account type, "service_account").