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

Update description of RegistrarCredit in g3doc architecture doc

Browse source 
This is a followup to [] that adds a similar explanation to our g3doc, warning that RegistrarCredits don't have any effect as implemented and may be removed.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=151041925
This commit is contained in:
nickfelt 2017-03-23 12:56:08 -07:00 • committed by Ben McIlwain
parent 5ffb424682
commit 015d07a9b6
1 changed files with 5 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/app-engine-architecture.md
View file

@ -366,10 +366,11 @@ registry codebase:
* `Registrar` -- These hold information about client registrars.
* `RegistrarContact` -- Registrars have contacts just as domains do. These are
stored in a special RegistrarContact entity.
* `RegistrarCredit` and `RegistrarCreditBalance` -- The system supports the
concept of a registrar credit balance, which is a pool of credit that the
registrar can use to offset amounts they owe. This might come from
promotions, for instance. These entities maintain registrars' balances.
* `RegistrarCredit` and `RegistrarCreditBalance` -- These entities implement
the concept of registrar "credits" which are pools of credit that would
apply to charges owed by the registrar. Note, however, that Nomulus
currently has no support for actually incorporating credits into billing
output, and these entities may be removed at any time.
* `Registry` -- These hold information about the TLDs supported by the
Registry system.
* `RegistryCursor` -- These entities are the predecessor to the Cursor