zydronium/google-nomulus
1
0
Fork 0
mirror of https://github.com/google/nomulus.git synced 2025-08-05 01:11:50 +02:00
Code Issues Projects Releases Packages Wiki Activity

Remove datastore related code (#1906)

Browse source
This commit is contained in:
Lai Jiang 2023-01-19 14:44:11 -05:00 • committed by GitHub
parent 913edb23ee
commit e41fd7877e
152 changed files with 886 additions and 4460 deletions
Download patch file Download diff file Expand all files Collapse all files

21
docs/operational-procedures/premium-list-management.md
View file

@ -4,12 +4,12 @@
Nomulus comes with a `StaticPremiumListPricingEngine` that determines premium
prices of domain labels (i.e. the part of the domain name without the TLD) by
checking for their presence on a list of prices in Datastore. `nomulus` is used
to load and update these lists from flat text files. The format of this list is
simple: It is a newline-delimited CSV text file with each line containing the
label and its price (including currency specifier in ISO-4217 format). Any
individual label may not appear more than once in the file. Here's an example of
the formatting:
checking for their presence on a list of prices in the database. `nomulus` is
used to load and update these lists from flat text files. The format of this
list is simple: It is a newline-delimited CSV text file with each line
containing the label and its price (including currency specifier in ISO-4217
format). Any individual label may not appear more than once in the file. Here's
an example of the formatting:
```
premium,USD 100
@ -28,7 +28,7 @@ location that is accessible to all members of your team (ideally in a source
control system for revision tracking). These files should be thought of as the
canonical versions of your premium lists. Note that there is no provided way to
reconstruct a premium list .txt file from the premium list that is loaded into
Datastore (though in principle it would be easy to do by writing a tool to do
the database (though in principle it would be easy to do by writing a tool to do
so), so don't lose those .txt files.
The nomulus repository contains an
@ -37,7 +37,7 @@ The nomulus repository contains an
## Creating a premium list
Once the file containing the premium prices is ready, run the
`create_premium_list` command to load it into Datastore as follows:
`create_premium_list` command to load it into the database as follows:
```shell
$ nomulus -e {ENVIRONMENT} create_premium_list -n exampletld -i exampletld.txt
@ -106,8 +106,9 @@ premiumList=Key<?>(EntityGroupRoot("cross-tld")/PremiumList("exampletld"))
## Listing all available premium lists
The `list_premium_lists` command is used to list all premium lists in Datastore.
It takes no arguments and displays a simple list of premium lists as follows:
The `list_premium_lists` command is used to list all premium lists in the
database. It takes no arguments and displays a simple list of premium lists as
follows:
```shell
$ nomulus -e {ENVIRONMENT} list_premium_lists

2
docs/operational-procedures/rde-deposits.md
View file

@ -26,7 +26,7 @@ need to implement a working and secure key store from which RDE can pull the
private key used to transmit the deposits via sFTP.
For each phase and TLD in the process, the system maintains a `Cursor` entity in
Datastore, which contains a timestamp indicating that everything before the
the database, which contains a timestamp indicating that everything before the
timestamp is current (except for RDE_UPLOAD_SFTP, which works a little
differently). Only if the current time is after the cursor time do the actions
check to see if they have work to do. For RDE, there are separate cursor types

6
docs/operational-procedures/reserved-list-management.md
View file

@ -82,7 +82,7 @@ reserved lists (see subsequent sections). The two naming patterns are thus:
## Creating a reserved list
Once the file containing the list of reserved terms is created, run the
`create_reserved_list` command to load it into Datastore as follows. For the
`create_reserved_list` command to load it into the database as follows. For the
purposes of this example, we are creating a common reserved list named
"common_bad-words".
@ -163,8 +163,8 @@ reservedLists=[Key<?>(EntityGroupRoot("cross-tld")/ReservedList("common_bad-word
## Listing all available reserved lists
The `list_reserved_lists` command is used to list all reserved lists in
Datastore. It takes no arguments and displays a simple list of reserved lists in
The `list_reserved_lists` command is used to list all reserved lists in the
database. It takes no arguments and displays a simple list of reserved lists in
newline-delimited format as follows:
```shell