Fixes

Author: okpedersen

README.md

@@ -370,10 +370,6 @@ We will use `cloudlabs-gcp.no` for this workshop. It is already configured in a
 
     Verify that the DNS record is created in the GCP console. And go to the newly created address `http://<your-id>.cloudlabs-gcp.no`. The propagation of the address can take some time. Try using `dig @8.8.8.8 <your-id>.cloudlabs-gcp.no` to see if the address is ready. Look for `;; ANSWER SECTION:`, and find a line that looks like `<your-id>.cloudlabs-gcp.no.  60 IN      A       34.160.83.207`. If you can't find the answer section, the DNS record might not be propagate yet (should not take more than a couple of minutes), or an error happened.
 
-3. For google cloud run, there are [multiple options](https://cloud.google.com/run/docs/mapping-custom-domains) to set up DNS. The recommended way is to set up a global external Application Load Balancer, similar to what we did for the frontend CDN., we'll use the [`google_cloud_run_domain_mapping`]
-
-    <!-- TODO: Backend DNS, Backend HTTPS? -->
-
 ## Extras
 
 ### Frontend HTTPS

solutions/terraform.tf

@@ -29,6 +29,8 @@ output "current_user_email" {
   value = data.google_client_openid_userinfo.current.email
 }
 
+data "google_project" "current" {}
+
 # This check will display a warning to the participants if they forget to set
 # the id local variable in main.tf
 check "id_is_set" {