Terraform provider docs update#2585
Terraform provider docs update#2585modular-magician merged 9 commits intoGoogleCloudPlatform:masterfrom
Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
|
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesNo diff detected in terraform-google-conversion. New Pull RequestsI built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed. |
|
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
|
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
danawillow
left a comment
There was a problem hiding this comment.
I think as best as possible it makes sense to use the product names from https://cloud.google.com/products/ (so say cloud when it says cloud, otherwise don't). I'm also not convinced we need "Google" in front of all of them since the user should already be aware that they're looking at Google stuff. What do you think?
|
@danawillow yeah it looks like the generated resources omit the "Google" somewhat frequently so probably time to make the cutover. |
|
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
|
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
519b1f4 to
00463c2
Compare
|
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
|
Took a look at the generated output, here are my notes on things that should probably be changed:
|
|
@danawillow yup I was just finishing my cleanup. I am thinking of keeping some of the cleanup for things like "BigTable" vs "Bigtable" in separate PR's because I'm not yet sure how it will affect the other downstreams. here are the current subcategories: |
|
Ah cool, looks like I got excited to review then 😛 A follow-up PR sounds totally fine. Let me know when this one is ready. |
|
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
|
@danawillow ok should be mostly clean now. I added #2590 for the yaml just in case there were downstream changes to other providers. |
|
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
7da3003 to
d3e1499
Compare
|
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
Tracked submodules are build/terraform-beta build/terraform-mapper build/terraform build/ansible build/inspec.
d3e1499 to
f877deb
Compare
upstream changes from hashicorp/terraform-provider-google#4795
I upstreamed the PR from @findkim, then had to make some updates on top of that. Including changes to the templating to generate the docs and manually adding subcategories for datasources.
I updated the datasources to have categories that are the same as their Resource equivalents. I believe this will nest them in the appropriate place, but we can revert that commit if we want to keep all datasources together.
Release Note Template for Downstream PRs (will be copied)