Copy that key and follow your provider’s advice for setting up the public key.
For example, in Clouse Source Repositories it looks like this:
I’ve already got a GitHub setup for my personal account.
Using ssh-agent gives us a way to config all this using the ~/.ssh/config files.
If it does not already exist just touch ~/.ssh/config to create it.
Adding the Cloud Source Repo section for this specific repository looks like this.
Note the hostname that this ssh keypair will apply to:
# New bit
Now if you try your git clone it’ll fail, even though it found the correct key to us based on the host:
$ git clone ssh://email@example.com@source.developers.google.com:2022/p/fleetrouting-app-ops/r/fleetrouting-app
Cloning into 'fleetrouting-app'...
The authenticity of host '[source.developers.google.com]:2022 ([188.8.131.52]:2022)' can't be established.
ECDSA key fingerprint is SHA256:AGvEpqYNMqsRNIviwyk4J4HM0lEylomDBKOWZsBn434.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[source.developers.google.com]:2022,[184.108.40.206]:2022'(ECDSA) to the list of known hosts.
firstname.lastname@example.org@source.developers.google.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.