chore: remove product_documentation_override from librarian.yaml#16791
chore: remove product_documentation_override from librarian.yaml#16791jskeet wants to merge 2 commits intogoogleapis:mainfrom
Conversation
| @@ -1,22 +1,22 @@ | |||
| Python Client for Cloud Identity and Access Management | |||
| ====================================================== | |||
|
|
|||
| |stable| |pypi| |versions| | |||
| |preview| |pypi| |versions| | |||
There was a problem hiding this comment.
This aspect is covered separately in #16790, but it didn't feel worth manually removing it.
There was a problem hiding this comment.
Code Review
This pull request updates product documentation links across numerous Python client libraries, primarily by generalizing specific deep links or removing documentation overrides in librarian.yaml and package metadata. Review feedback indicates that entirely removing the product_documentation field in several packages—specifically google-cloud-common, google-cloud-compute-v1beta, google-cloud-firestore, and google-cloud-datastore—results in empty link targets in the generated README.rst files. This creates invalid reStructuredText that breaks documentation builds. The reviewer recommends using a fallback URL, such as https://cloud.google.com/, to ensure the documentation remains valid and functional.
| @@ -9,7 +9,6 @@ | |||
| "library_type": "CORE", | |||
| "name": "common", | |||
There was a problem hiding this comment.
Removing the product_documentation field entirely causes the generated README files to have empty link targets (e.g., .. _Google Cloud Common: ), which is invalid reStructuredText and breaks the documentation build. Instead of removing the field, please update it to a valid fallback URL such as https://cloud.google.com/.
| "name": "common", | |
| "name_pretty": "Google Cloud Common", | |
| "product_documentation": "https://cloud.google.com/", |
References
- It is acceptable to use placeholder values in metadata files to avoid blocking merges when the correct value is not yet determined.
| @@ -10,7 +10,6 @@ | |||
| "library_type": "GAPIC_AUTO", | |||
| "name": "google-cloud-compute-v1beta", | |||
| "name_pretty": "Compute Engine", | |||
There was a problem hiding this comment.
Removing the product_documentation field entirely causes the generated README files to have empty link targets, which is invalid reStructuredText. Instead of removing the field, please update it to a valid fallback URL such as https://cloud.google.com/.
| "name_pretty": "Compute Engine", | |
| "name_pretty": "Compute Engine", | |
| "product_documentation": "https://cloud.google.com/", |
References
- It is acceptable to use placeholder values in metadata files to avoid blocking merges when the correct value is not yet determined.
| @@ -10,7 +10,6 @@ | |||
| "library_type": "GAPIC_COMBO", | |||
| "name": "firestore", | |||
| "name_pretty": "Cloud Firestore API", | |||
There was a problem hiding this comment.
Removing the product_documentation field entirely causes the generated README files to have empty link targets, which is invalid reStructuredText. Instead of removing the field, please update it to a valid fallback URL such as https://cloud.google.com/.
| "name_pretty": "Cloud Firestore API", | |
| "name_pretty": "Cloud Firestore API", | |
| "product_documentation": "https://cloud.google.com/", |
References
- It is acceptable to use placeholder values in metadata files to avoid blocking merges when the correct value is not yet determined.
| @@ -10,7 +10,6 @@ | |||
| "library_type": "GAPIC_COMBO", | |||
| "name": "datastore", | |||
| "name_pretty": "Google Cloud Datastore API", | |||
There was a problem hiding this comment.
Removing the product_documentation field entirely causes the generated README files to have empty link targets, which is invalid reStructuredText. Instead of removing the field, please update it to a valid fallback URL such as https://cloud.google.com/.
| "name_pretty": "Google Cloud Datastore API", | |
| "name_pretty": "Google Cloud Datastore API", | |
| "product_documentation": "https://cloud.google.com/", |
References
- It is acceptable to use placeholder values in metadata files to avoid blocking merges when the correct value is not yet determined.
| .. _Google Cloud Common: | ||
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/common/latest/summary_overview | ||
| .. _Product Documentation: https://cloud.google.com | ||
| .. _Product Documentation: |
There was a problem hiding this comment.
These link targets are empty, which is invalid reStructuredText and will result in broken links in the rendered documentation. Based on other changes in this PR (e.g., for google-cloud-quotas), these should point to https://cloud.google.com/ if a more specific product page is not available. This issue also occurs on lines 33 and 107 of this file, and in the corresponding docs/README.rst.
| .. _Google Cloud Common: | |
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/common/latest/summary_overview | |
| .. _Product Documentation: https://cloud.google.com | |
| .. _Product Documentation: | |
| .. _Google Cloud Common: https://cloud.google.com/ | |
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/common/latest/summary_overview | |
| .. _Product Documentation: https://cloud.google.com/ |
| .. _Compute Engine: | ||
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/google-cloud-compute-v1beta/latest/summary_overview | ||
| .. _Product Documentation: https://cloud.google.com/compute/ | ||
| .. _Product Documentation: |
There was a problem hiding this comment.
These link targets are empty, which is invalid reStructuredText. They should point to a valid URL, such as https://cloud.google.com/. This issue also occurs on lines 33 and 107 of this file, and in the corresponding docs/README.rst.
| .. _Compute Engine: | |
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/google-cloud-compute-v1beta/latest/summary_overview | |
| .. _Product Documentation: https://cloud.google.com/compute/ | |
| .. _Product Documentation: | |
| .. _Compute Engine: https://cloud.google.com/ | |
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/google-cloud-compute-v1beta/latest/summary_overview | |
| .. _Product Documentation: https://cloud.google.com/ |
| .. _Cloud Firestore API: | ||
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/firestore/latest/summary_overview | ||
| .. _Product Documentation: https://cloud.google.com/firestore | ||
| .. _Product Documentation: |
There was a problem hiding this comment.
These link targets are empty, which is invalid reStructuredText. They should point to a valid URL, such as https://cloud.google.com/. This issue also occurs on lines 33 and 107 of this file, and in the corresponding docs/README.rst.
| .. _Cloud Firestore API: | |
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/firestore/latest/summary_overview | |
| .. _Product Documentation: https://cloud.google.com/firestore | |
| .. _Product Documentation: | |
| .. _Cloud Firestore API: https://cloud.google.com/ | |
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/firestore/latest/summary_overview | |
| .. _Product Documentation: https://cloud.google.com/ |
| .. _Google Cloud Datastore API: | ||
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/datastore/latest/summary_overview | ||
| .. _Product Documentation: https://cloud.google.com/datastore | ||
| .. _Product Documentation: |
There was a problem hiding this comment.
These link targets are empty, which is invalid reStructuredText. They should point to a valid URL, such as https://cloud.google.com/. This issue also occurs on lines 37 and 111 of this file, and in the corresponding docs/README.rst.
| .. _Google Cloud Datastore API: | |
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/datastore/latest/summary_overview | |
| .. _Product Documentation: https://cloud.google.com/datastore | |
| .. _Product Documentation: | |
| .. _Google Cloud Datastore API: https://cloud.google.com/ | |
| .. _Client Library Documentation: https://cloud.google.com/python/docs/reference/datastore/latest/summary_overview | |
| .. _Product Documentation: https://cloud.google.com/ |
|
@daniel-sanche: I suggest that links that are just changed are probably accepted, but where we end up with no value at all, we go one of two ways:
I think the split is like this: API-based libraries:
Handwritten libraries:
|
|
Actually, for the handwritten libraries, presumably the README isn't generated anyway, so .repo-metadata.json doesn't matter, unless it's being consumed elsewhere. So we should be able to get rid of the field in librarian.yaml after all - but we need to upstream the values to sdk.yaml first. |
|
Regenerating for a second PR, based on googleapis/librarian#5573 |
|
The Spanner changes aren't intended to be in this PR - will revert those in the second PR; ignore them for now. |
Towards googleapis/librarian#5466