Recover Google Cloud Shell Home Directory

google-cloud-platformgoogle-cloud-shell

My G Suite user which I log into GCP with has been renamed from firstname@domain.com to firstname.lastname@domain.com

I have now logged back into Cloud Shell and my home directory content is gone.

Is there any way of recovering this?

Thanks

Best Answer

Per the documentation, you have some limitations when working with the shell, as stated before you shouldn't have important information stored over there and should be moved to Google Cloud Storage if needed.

There's no way to restore the data lost once your profile was deleted.

Related Solutions

How to modify the existing access scope of a Google Cloud Platform service account

I believe eventually you will be able to do this using IAM permissions. At the moment I do not see the options to add Cloud DNS roles in the IAM Console. In order to authorize requests to Cloud DNS you must use one of the scopes describe in this article.

i.e.

https://www.googleapis.com/auth/ndev.clouddns.readwrite
https://cloud.google.com/dns/api/authorization

If you are using the default service account, the scope has to be defined during the VM creation in the scope flag.

i.e.

gcloud compute --project "Myproject" instances create "instance-8" --zone "us-central1-f" --machine-type "n1-standard-1" --network "default" --maintenance-policy "MIGRATE" --scopes default="https://www.googleapis.com/auth/devstorage.full_control","https://www.googleapis.com/auth/ndev.clouddns.readwrite" --image "/debian-cloud/debian-8-jessie-v20161020" --boot-disk-size "10" --boot-disk-type "pd-standard" --boot-disk-device-name "instance-8"

If you associated the VM to a non-default service account during its creation, you can add Editor or Owner permissions to that account in the IAM Console. Nevertheless this might provide a wider scope that the one you are looking for.

Google Cloud Platform – Routing with VPCs Peered in a Partially Connected Mesh Topology

According to the GCP documentation, it is not possible for vpcB and vpcC to communicate:

Only directly peered networks can communicate. Transitive peering is not supported. In other words, if VPC network N1 is peered with N2 and N3, but N2 and N3 are not also directly connected, VPC network N2 cannot communicate with VPC network N3 over the peering.

Also, VPN connections are not exported to peered VPCs:

The following types of endpoints/resources are NOT propagated to directly peered networks: Static routes, VPNs

Best Answer

Related Solutions

How to modify the existing access scope of a Google Cloud Platform service account

Google Cloud Platform – Routing with VPCs Peered in a Partially Connected Mesh Topology

Related Topic