Change Details

To clone Git repositories, we need a key, but when provisioning a new server, if we generate a new key, it won't be available on Git repositories hosting like GitHub. Perhaps a master key would be more pertinent, if so, that's a candidate for Vault.

To clone Git repositories, we need a key, but when provisioning a new server, if we generate a new key, it won't be available on Git repositories hosting like GitHub. So, currently, deployment fails like this: ``` ---------- ID: /var/51-wwwroot/api Function: git.latest Name: ssh://vcs@devcentral.nasqueron.org:5022/source/api.git Result: False Comment: Failed to check remote refs: Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Started: 13:25:53.395911 Duration: 113.33 ms Changes: ``` Perhaps a master key would be more pertinent, if so, that's a candidate for Vault.

To clone Git repositories, we need a key, but when provisioning a new server, if we generate a new key, it won't be available on Git repositories hosting like GitHub. So, currently, deployment fails like this: ``` ---------- ID: /var/51-wwwroot/api Function: git.latest Name: ssh://vcs@devcentral.nasqueron.org:5022/source/api.git Result: False Comment: Failed to check remote refs: Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Started: 13:25:53.395911 Duration: 113.33 ms Changes: ``` Perhaps a master key would be more pertinent, if so, that's a candidate for Vault.