Cloud Storage avis

Andrea V. · Examiné il y a 11 jours

Cruz Hernandez L. · Examiné il y a 11 jours

Carlos C. · Examiné il y a 11 jours

Jayson C. · Examiné il y a 11 jours

Camilo M. · Examiné il y a 11 jours

Henry G. · Examiné il y a 11 jours

Богдан В. · Examiné il y a 11 jours

Namathoti N. · Examiné il y a 11 jours

Kevin Julian C. · Examiné il y a 11 jours

ARDRA A NAIR S. · Examiné il y a 11 jours

Namathoti N. · Examiné il y a 11 jours

Mahdi M. · Examiné il y a 11 jours

Poor instructions and steps for Customer-supplied encryption keys and the encryption type setup on the bucket. Being they don't match one cannot progress in the lab. Also had to enable versioning myself there was not setup or item in the lab to do this. Very poorly writen.

Thomas P. · Examiné il y a 11 jours

Thomas S. · Examiné il y a 11 jours

Namathoti N. · Examiné il y a 11 jours

Michael L. · Examiné il y a 11 jours

Ananya Gupta A. · Examiné il y a 11 jours

Welber C. · Examiné il y a 11 jours

VenkataNarendar M. · Examiné il y a 11 jours

Eduardo L. · Examiné il y a 11 jours

Spent the bulk of my time figuring out the issues with CSEK because it was not in the instructions. When following instructions i got a 412 error because CSEK was in full enforcement. I had to do the following to change the policy and then i was able to upload using my key. This should be part of the steps: cat > encryption_enforcement.json <<'EOF' { "csekEnforcement": { "restrictionMode": "NotRestricted" } } EOF gcloud storage buckets update gs://$BUCKET_NAME_1 \ --encryption-enforcement-file=encryption_enforcement.json verify gcloud storage buckets describe gs://$BUCKET_NAME_1 --format="yaml(csek_enforcement)" then run gsutil cp setup2.html gs://$BUCKET_NAME_1/

kice n. · Examiné il y a 11 jours

I missed some code along the line

Ime E. · Examiné il y a 11 jours

Nagsen K. · Examiné il y a 11 jours

Shantanu d. · Examiné il y a 11 jours

BATTULA B. · Examiné il y a 11 jours