chore(migration): Update common files for batch migration (#11648)

.release-please-manifest.json

@@ -11,6 +11,7 @@
     "packages/google-cloud-apigee-registry": "0.6.3",
     "packages/google-cloud-appengine-logging": "1.3.1",
     "packages/google-cloud-artifact-registry": "1.8.3",
+    "packages/google-cloud-assured-workloads": "1.10.3",
     "packages/google-cloud-bare-metal-solution": "1.5.0",
     "packages/google-cloud-batch": "0.17.0",
     "packages/google-cloud-beyondcorp-appconnections": "0.4.3",
@@ -54,6 +55,7 @@
     "packages/google-cloud-eventarc": "1.9.2",
     "packages/google-cloud-eventarc-publishing": "0.6.3",
     "packages/google-cloud-functions": "1.13.2",
+    "packages/google-cloud-gke-backup": "0.5.2",
     "packages/google-cloud-gke-connect-gateway": "0.8.3",
     "packages/google-cloud-gke-multicloud": "0.6.2",
     "packages/google-cloud-iam": "2.12.1",
@@ -72,7 +74,9 @@
     "packages/google-cloud-network-connectivity": "2.0.2",
     "packages/google-cloud-network-management": "1.11.0",
     "packages/google-cloud-network-security": "0.9.3",
+    "packages/google-cloud-network-services": "0.5.4",
     "packages/google-cloud-notebooks": "1.8.0",
+    "packages/google-cloud-optimization": "1.5.0",
     "packages/google-cloud-orchestration-airflow": "1.9.1",
     "packages/google-cloud-phishing-protection": "1.9.1",
     "packages/google-cloud-policy-troubleshooter": "1.9.0",

packages/google-cloud-assured-workloads/.repo-metadata.json

@@ -7,7 +7,7 @@
     "release_level": "stable",
     "language": "python",
     "library_type": "GAPIC_AUTO",
-    "repo": "googleapis/python-assured-workloads",
+    "repo": "googleapis/google-cloud-python",
     "distribution_name": "google-cloud-assured-workloads",
     "api_id": "assuredworkloads.googleapis.com",
     "default_version": "v1",

packages/google-cloud-assured-workloads/CONTRIBUTING.rst

@@ -35,21 +35,21 @@ Using a Development Checkout
 You'll have to create a development environment using a Git checkout:
 
 - While logged into your GitHub account, navigate to the
-  ``python-assured-workloads`` `repo`_ on GitHub.
+  ``google-cloud-python`` `repo`_ on GitHub.
 
-- Fork and clone the ``python-assured-workloads`` repository to your GitHub account by
+- Fork and clone the ``google-cloud-python`` repository to your GitHub account by
   clicking the "Fork" button.
 
-- Clone your fork of ``python-assured-workloads`` from your GitHub account to your local
+- Clone your fork of ``google-cloud-python`` from your GitHub account to your local
   computer, substituting your account username and specifying the destination
-  as ``hack-on-python-assured-workloads``.  E.g.::
+  as ``hack-on-google-cloud-python``.  E.g.::
 
    $ cd ${HOME}
-   $ git clone [email protected]:USERNAME/python-assured-workloads.git hack-on-python-assured-workloads
-   $ cd hack-on-python-assured-workloads
-   # Configure remotes such that you can pull changes from the googleapis/python-assured-workloads
+   $ git clone [email protected]:USERNAME/google-cloud-python.git hack-on-google-cloud-python
+   $ cd hack-on-google-cloud-python
+   # Configure remotes such that you can pull changes from the googleapis/google-cloud-python
    # repository into your local repository.
-   $ git remote add upstream [email protected]:googleapis/python-assured-workloads.git
+   $ git remote add upstream [email protected]:googleapis/google-cloud-python.git
    # fetch and merge changes from upstream into main
    $ git fetch upstream
    $ git merge upstream/main
@@ -60,7 +60,7 @@ repo, from which you can submit a pull request.
 To work on the codebase and run the tests, we recommend using ``nox``,
 but you can also use a ``virtualenv`` of your own creation.
 
-.. _repo: https://github.com/googleapis/python-assured-workloads
+.. _repo: https://github.com/googleapis/google-cloud-python
 
 Using ``nox``
 =============
@@ -113,7 +113,7 @@ Coding Style
    export GOOGLE_CLOUD_TESTING_BRANCH="main"
 
   By doing this, you are specifying the location of the most up-to-date
-  version of ``python-assured-workloads``. The
+  version of ``google-cloud-python``. The
   remote name ``upstream`` should point to the official ``googleapis``
   checkout and the branch should be the default branch on that remote (``main``).
 
@@ -209,7 +209,7 @@ The `description on PyPI`_ for the project comes directly from the
 ``README``. Due to the reStructuredText (``rst``) parser used by
 PyPI, relative links which will work on GitHub (e.g. ``CONTRIBUTING.rst``
 instead of
-``https://github.com/googleapis/python-assured-workloads/blob/main/CONTRIBUTING.rst``)
+``https://github.com/googleapis/google-cloud-python/blob/main/CONTRIBUTING.rst``)
 may cause problems creating links or rendering the description.
 
 .. _description on PyPI: https://pypi.org/project/google-cloud-assured-workloads
@@ -236,7 +236,7 @@ We support:
 
 Supported versions can be found in our ``noxfile.py`` `config`_.
 
-.. _config: https://github.com/googleapis/python-assured-workloads/blob/main/packages/google-cloud-assured-workloads/noxfile.py
+.. _config: https://github.com/googleapis/google-cloud-python/blob/main/packages/google-cloud-assured-workloads/noxfile.py
 
 
 **********

packages/google-cloud-assured-workloads/docs/conf.py

@@ -156,7 +156,7 @@
 html_theme_options = {
     "description": "Google Cloud Client Libraries for google-cloud-assured-workloads",
     "github_user": "googleapis",
-    "github_repo": "python-assured-workloads",
+    "github_repo": "google-cloud-python",
     "github_banner": True,
     "font_family": "'Roboto', Georgia, sans",
     "head_font_family": "'Roboto', Georgia, serif",

packages/google-cloud-gke-backup/.repo-metadata.json

@@ -8,7 +8,7 @@
     "release_level": "preview",
     "language": "python",
     "library_type": "GAPIC_AUTO",
-    "repo": "googleapis/python-gke-backup",
+    "repo": "googleapis/google-cloud-python",
     "distribution_name": "google-cloud-gke-backup",
     "api_id": "gkebackup.googleapis.com",
     "default_version": "v1",

packages/google-cloud-gke-backup/CONTRIBUTING.rst

@@ -35,21 +35,21 @@ Using a Development Checkout
 You'll have to create a development environment using a Git checkout:
 
 - While logged into your GitHub account, navigate to the
-  ``python-gke-backup`` `repo`_ on GitHub.
+  ``google-cloud-python`` `repo`_ on GitHub.
 
-- Fork and clone the ``python-gke-backup`` repository to your GitHub account by
+- Fork and clone the ``google-cloud-python`` repository to your GitHub account by
   clicking the "Fork" button.
 
-- Clone your fork of ``python-gke-backup`` from your GitHub account to your local
+- Clone your fork of ``google-cloud-python`` from your GitHub account to your local
   computer, substituting your account username and specifying the destination
-  as ``hack-on-python-gke-backup``.  E.g.::
+  as ``hack-on-google-cloud-python``.  E.g.::
 
    $ cd ${HOME}
-   $ git clone [email protected]:USERNAME/python-gke-backup.git hack-on-python-gke-backup
-   $ cd hack-on-python-gke-backup
-   # Configure remotes such that you can pull changes from the googleapis/python-gke-backup
+   $ git clone [email protected]:USERNAME/google-cloud-python.git hack-on-google-cloud-python
+   $ cd hack-on-google-cloud-python
+   # Configure remotes such that you can pull changes from the googleapis/google-cloud-python
    # repository into your local repository.
-   $ git remote add upstream [email protected]:googleapis/python-gke-backup.git
+   $ git remote add upstream [email protected]:googleapis/google-cloud-python.git
    # fetch and merge changes from upstream into main
    $ git fetch upstream
    $ git merge upstream/main
@@ -60,7 +60,7 @@ repo, from which you can submit a pull request.
 To work on the codebase and run the tests, we recommend using ``nox``,
 but you can also use a ``virtualenv`` of your own creation.
 
-.. _repo: https://github.com/googleapis/python-gke-backup
+.. _repo: https://github.com/googleapis/google-cloud-python
 
 Using ``nox``
 =============
@@ -113,7 +113,7 @@ Coding Style
    export GOOGLE_CLOUD_TESTING_BRANCH="main"
 
   By doing this, you are specifying the location of the most up-to-date
-  version of ``python-gke-backup``. The
+  version of ``google-cloud-python``. The
   remote name ``upstream`` should point to the official ``googleapis``
   checkout and the branch should be the default branch on that remote (``main``).
 
@@ -209,7 +209,7 @@ The `description on PyPI`_ for the project comes directly from the
 ``README``. Due to the reStructuredText (``rst``) parser used by
 PyPI, relative links which will work on GitHub (e.g. ``CONTRIBUTING.rst``
 instead of
-``https://github.com/googleapis/python-gke-backup/blob/main/CONTRIBUTING.rst``)
+``https://github.com/googleapis/google-cloud-python/blob/main/CONTRIBUTING.rst``)
 may cause problems creating links or rendering the description.
 
 .. _description on PyPI: https://pypi.org/project/google-cloud-gke-backup
@@ -236,7 +236,7 @@ We support:
 
 Supported versions can be found in our ``noxfile.py`` `config`_.
 
-.. _config: https://github.com/googleapis/python-gke-backup/blob/main/packages/google-cloud-gke-backup/noxfile.py
+.. _config: https://github.com/googleapis/google-cloud-python/blob/main/packages/google-cloud-gke-backup/noxfile.py
 
 
 **********

packages/google-cloud-gke-backup/docs/conf.py

@@ -156,7 +156,7 @@
 html_theme_options = {
     "description": "Google Cloud Client Libraries for google-cloud-gke-backup",
     "github_user": "googleapis",
-    "github_repo": "python-gke-backup",
+    "github_repo": "google-cloud-python",
     "github_banner": True,
     "font_family": "'Roboto', Georgia, sans",
     "head_font_family": "'Roboto', Georgia, serif",

packages/google-cloud-network-services/.repo-metadata.json

@@ -7,7 +7,7 @@
     "release_level": "preview",
     "language": "python",
     "library_type": "GAPIC_AUTO",
-    "repo": "googleapis/python-network-services",
+    "repo": "googleapis/google-cloud-python",
     "distribution_name": "google-cloud-network-services",
     "api_id": "networkservices.googleapis.com",
     "default_version": "v1",