From 9eaa69c7c220dafeb659eb37759e6a7d17b0ae43 Mon Sep 17 00:00:00 2001 From: sarahcaseybot Date: Fri, 12 May 2023 12:32:02 -0400 Subject: [PATCH] Change Registry object reference to Tld in configuration.md (#2021) --- docs/configuration.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/configuration.md b/docs/configuration.md index 1c59f8fc9..1db9024a4 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -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 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 -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. ## Initial configuration @@ -177,7 +177,7 @@ SecretManager to configure accordingly, for example: ## 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, such as the create/renew price of a domain name, the pricing engine 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 -Nomulus is in the process of being ported to Cloud SQL. As such, parts of the -system already require access to Cloud SQL and the necessary configuration +Nomulus requires access to Cloud SQL and thus the necessary configuration must be applied. ### Create Postgres Cloud SQL Instance