chore(migration): Migrate code from googleapis/python-dns into packages/google-cloud-dns

[parthea]

See #11024.

This PR should be merged with a merge-commit, not a squash-commit, in order to preserve the git history.

[gemini-code-assist]

Summary of Changes

Hello @parthea, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request completes the migration of the Google Cloud DNS Python client library into the monorepo structure. The change involves moving all source code, tests, documentation, and build configurations into the packages/google-cloud-dns directory. This consolidation streamlines development workflows and ensures consistent tooling across Google Cloud Python client libraries. The migration is designed to preserve the full git history of the python-dns library.

Highlights

• Library Migration: The entire python-dns client library has been moved to packages/google-cloud-dns/ to centralize it within the monorepo structure.
• Standardized Configuration: New build, linting, and testing configuration files (.coveragerc, .flake8, noxfile.py, pytest.ini, renovate.json, setup.py) have been added to align with monorepo standards.
• Updated Documentation: Comprehensive documentation, including CHANGELOG.md, CONTRIBUTING.rst, README.rst, and Sphinx configuration, has been added/updated for the new package location.
• Migration Script Enhancements: The single-library.git-migrate-history.sh script was updated to correctly handle submodules and remove nested .git directories during the migration process, ensuring a clean transfer of history.

Changelog

• packages/google-cloud-dns/
  • Added all source code, documentation, and configuration files for the google-cloud-dns Python client library. This includes build and linting configurations (.coveragerc, .flake8, .pre-commit-config.yaml, noxfile.py, pytest.ini, setup.py), project metadata (.librarian/state.yaml, .repo-metadata.json), core library modules (google/cloud/dns/*.py), comprehensive documentation (CHANGELOG.md, CODE_OF_CONDUCT.md, CONTRIBUTING.rst, LICENSE, README.rst, SECURITY.md, and the docs/ directory with Sphinx configurations), utility scripts (scripts/), and testing infrastructure (testing/, tests/).
• scripts/split_repo_migration/single-library.git-migrate-history.sh
  • Modified the script to include --recurse-submodules when cloning the source repository.
  • Enhanced the tree-filter command to handle and remove nested .git directories within submodules, preventing issues during history migration.
  • Applied --recurse-submodules and .git directory removal to the validation clone as well.

Activity

• No specific activity (comments, reviews, etc.) was provided in the context.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This PR migrates the google-cloud-dns library into the monorepo. The changes are extensive, covering source code, documentation, and CI/CD configuration. Overall, the migration looks good, but I've found several areas where references to the old repository (googleapis/python-dns) and outdated configurations persist. These will need to be updated to ensure CI, documentation, and repository management tools function correctly in the new monorepo structure. Key areas for improvement include updating repository URLs in metadata and documentation files, correcting CI configuration paths, and fixing a typo in the library's __init__.py that would affect documentation generation.

I am having trouble creating individual review comments. Click here to see my feedback.

packages/google-cloud-dns/.kokoro/continuous/common.cfg (17-26)

The build_file and TRAMPOLINE_BUILD_FILE paths appear to reference the old python-dns repository structure. These paths likely need to be updated to reflect the new monorepo structure (e.g., packages/google-cloud-dns/...) to prevent CI failures. This issue is present in other Kokoro configuration files as well.

packages/google-cloud-dns/.kokoro/noxfile.py (92)

The ALL_VERSIONS list is missing Python 3.14. Other CI configurations attempt to run sample tests for this version, which will fail because the py-3.14 nox session will not be defined. Please add 3.14 to this list.

ALL_VERSIONS = ["3.7", "3.8", "3.9", "3.10", "3.11", "3.12", "3.13", "3.14"]

packages/google-cloud-dns/.repo-metadata.json (10-14)

There are a couple of issues in this metadata file:

1. The repo field on line 10 points to the old googleapis/python-dns repository. It should be updated to point to the current monorepo, googleapis/google-cloud-python.
2. The codeowner_team field on line 14 is empty. Based on the comment in .github/CODEOWNERS, this should be populated, likely with @googleapis/yoshi-python.

    "repo": "googleapis/google-cloud-python",
    "distribution_name": "google-cloud-dns",
    "requires_billing": true,
    "default_version": "",
    "codeowner_team": "@googleapis/yoshi-python",

packages/google-cloud-dns/google/cloud/dns/init.py (19-24)

There's a typo in the docstring references to other classes. google.cloud.DNS should be google.cloud.dns. This will cause issues with documentation generation.

- :class:`~google.cloud.dns.zone.ManagedZone` represents an collection of
  tables.
- :class:`~google.cloud.dns.resource_record_set.ResourceRecordSet` represents
  a single resource definition within a zone.
- :class:`~google.cloud.dns.changes.Changes` represents a set of changes
  (adding/deleting resource record sets) to a zone.

packages/google-cloud-dns/.github/ISSUE_TEMPLATE/bug_report.md (13)

The link to search for existing issues points to the old python-dns repository. This should be updated to point to the issues in the current monorepo to ensure users are searching in the correct place.

  - Search the issues already opened: https://github.com/googleapis/google-cloud-python/issues

packages/google-cloud-dns/.github/PULL_REQUEST_TEMPLATE.md (2)

The link for opening a new issue points to the old python-dns repository. This should be updated to the new repository's issue creation page.

- [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/google-cloud-python/issues/new/choose) before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea

packages/google-cloud-dns/.github/workflows/unittest.yml (16-21)

The versions of actions/checkout and actions/setup-python are older than in other workflows. For consistency and to use the latest features, please update them to v6.

    - name: Checkout
      uses: actions/checkout@v6
    - name: Setup Python
      uses: actions/setup-python@v6
      with:
        python-version: ${{ matrix.python }}

packages/google-cloud-dns/CONTRIBUTING.rst (63)

This file contains several references to the old python-dns repository. These should be updated to point to the new monorepo location. For example, the repo link on this line should be updated.

.. _repo: https://github.com/googleapis/google-cloud-python

packages/google-cloud-dns/docs/conf.py (159)

The github_repo configuration points to the old python-dns repository. This should be updated to google-cloud-python to ensure documentation links are correct.

    "github_repo": "google-cloud-python",

packages/google-cloud-dns/setup.py (73)

The url in setup.py points to the old python-dns repository. This should be updated to the URL of the monorepo.

    url="https://github.com/googleapis/google-cloud-python",

[parthea]

Code is ready for review but not merge