Change Registry object reference to Tld in configuration.md (#2021)

This commit is contained in:
sarahcaseybot 2023-05-12 12:32:02 -04:00 committed by GitHub
parent 8c92b5f4cf
commit 9eaa69c7c2

View file

@ -4,7 +4,7 @@ There are multiple different kinds of configuration that go into getting a
working registry system up and running. Broadly speaking, configuration works in working registry system up and running. Broadly speaking, configuration works in
two ways -- globally, for the entire sytem, and per-TLD. Global configuration is two ways -- globally, for the entire sytem, and per-TLD. Global configuration is
managed by editing code and deploying a new version, whereas per-TLD managed by editing code and deploying a new version, whereas per-TLD
configuration is data that lives in the database in `Registry` entities, and is configuration is data that lives in the database in `Tld` entities, and is
updated by running `nomulus` commands without having to deploy a new version. updated by running `nomulus` commands without having to deploy a new version.
## Initial configuration ## Initial configuration
@ -177,7 +177,7 @@ SecretManager to configure accordingly, for example:
## Per-TLD configuration ## Per-TLD configuration
`Registry` entities, which are persisted to the database, are used for per-TLD `Tld` entities, which are persisted to the database, are used for per-TLD
configuration. They contain any kind of configuration that is specific to a TLD, configuration. They contain any kind of configuration that is specific to a TLD,
such as the create/renew price of a domain name, the pricing engine such as the create/renew price of a domain name, the pricing engine
implementation, the DNS writer implementation, whether escrow exports are implementation, the DNS writer implementation, whether escrow exports are
@ -194,8 +194,7 @@ and thus do not require code pushes to update.
## Cloud SQL Configuration ## Cloud SQL Configuration
Nomulus is in the process of being ported to Cloud SQL. As such, parts of the Nomulus requires access to Cloud SQL and thus the necessary configuration
system already require access to Cloud SQL and the necessary configuration
must be applied. must be applied.
### Create Postgres Cloud SQL Instance ### Create Postgres Cloud SQL Instance