Skip to content

Commit

Permalink
Updated readme file (#1056)
Browse files Browse the repository at this point in the history
  • Loading branch information
zyh0613 committed Aug 9, 2023
1 parent 73734af commit e79c75a
Showing 1 changed file with 7 additions and 10 deletions.
17 changes: 7 additions & 10 deletions tools/gdns-zdns-project-bulk-migration/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ the reason why the projects are not ready to migrate. The reasons can include
but not limited to:
- inaccessible project (project id does not exist or the current user does not have permission to access the project)
- inaccessbile metrics (the current user doesn not have permission to access the project's Cloud Monitoring metrics)
- not ready for migration
- not ready for migration (incompatible with ZonalOnly settings)
- have been using Zonal DNS already (no action needed)

If you have any questions about the migration, please refer to https://cloud.google.com/compute/docs/internal-dns#migrating-to-zonal for more information.
Expand Down Expand Up @@ -69,7 +69,7 @@ bash migration --project_id=p1 --dry_run=false # p1 will be migrated if it is re
The script prints out a summary at the end to tell the users which projects are:
- inaccessible project (project id does not exist or the current user does not have permission to access the project)
- inaccessbile metrics (the current user doesn not have permission to access the project's Cloud Monitoring metrics)
- not ready for migration
- not ready for migration (incompatible with ZonalOnly settings)
- have been using Zonal DNS already (no action needed)
- ready for migration (and migrated if `--dry_run=false`)

Expand Down Expand Up @@ -185,14 +185,11 @@ The following 2 projects were ready and migrated to Zonal DNS:
```

## Links

- Zonal DNS Migration: https://cloud.google.com/compute/docs/internal-dns#migrating-to-zonal
## Rollback

## Licensing
If you see any issues or for any other reasons you want to rollback after the
migration, please see https://cloud.google.com/compute/docs/internal-dns#disabling-zonal-dns.

One really important part: Give your project a proper license. Here you should
state what the license is and how to find the text version of the license.
Something like:
## Links

"The code in this project is licensed under MIT license."
- Zonal DNS Migration: https://cloud.google.com/compute/docs/internal-dns#migrating-to-zonal

0 comments on commit e79c75a

Please sign in to comment.