resource "google_api_gateway_api" "api_gw" {
provider = google-beta
api_id = "my-api"
}
resource "google_api_gateway_gateway" "api_gw" {
provider = google-beta
api_config = google_api_gateway_api_config.api_gw.id
gateway_id = "my-gateway"
}
Am I the only person here that thinks this resource naming is absurd? I should be able to look at these resource names and immediately understand what is going on here. This is nothing but confusion.
I wish I could say this is the only example of this ridiculousness in the Google/Google-beta provider (speaking of, two providers? Really?) but it’s not.
https://old.reddit.com/r/youtube/comments/195octe/youtube_started_slowing_video_buffer_with_adblock/
At some point, Google and YouTube deserve some consequences.
I have always wanted to use Firebase and Google Cloud for more and more projects. My last support experience with AWS was bad enough that I decided it was time to make the leap. Galaxycow is now using Firebase hosting. Bear with me for the SSL errors for a little while.
It’s interesting to me to see who’s doing the actual tracking. Thanks to Safari, it seems the worst violators in my bubble are… tech sites.
