hashicorp / terraform-provider-google

Terraform Provider for Google Cloud Platform
https://registry.terraform.io/providers/hashicorp/google/latest/docs
Mozilla Public License 2.0
2.33k stars 1.73k forks source link

Add disclaimer for google_firebase_hosting_site about UI activation in Firebase Console #19110

Open AlexanderLid opened 2 months ago

AlexanderLid commented 2 months ago

What kind of contribution is this issue about?

Other (specify in details)

Details

When using Terraform to create a Firebase Hosting site for the first time, the site does not appear in the Firebase Console. Even though it's successfully created, the UI may still prompt you to "Get Started", making it seem like the site and firebase hosting isn't activated.

Terraform users expect it to be activated through the resources, but in this case, you need to manually click through the "Get Started" steps in the Firebase Console to make the site and domains visible. These steps don’t actually do anything but are required for the site to show up.

Suggested Disclaimer: After creating a Firebase Hosting site with Terraform, you may need to click through the "Get Started" steps in the Firebase Console to make the site visible. These steps do nothing.

References

https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/firebase_hosting_site

b/360875879

rainshen49 commented 2 months ago

@AlexanderLid Does it still happen after you publish the first release?

The Firebase Console doesn't recognize any meaningful progress in Firebase Hosting until you make a first release. You can see that this is the behavior even when not using Terraform.

  1. Go to Firebase Console > Hosting
  2. Go through Get Started, but don't actually execute the steps.
  3. Go to some other page than Hosting
  4. Come back to Hosting.
  5. You'd see the Get Started page again.
AlexanderLid commented 2 months ago

@rainshen49 You are correct, the get started steps are back. Wierd behaviour.

rainshen49 commented 2 months ago

To the Terraform maintainers: this is not a Terraform issue. Please close.