mirror of
https://github.com/google/nomulus.git
synced 2025-04-30 03:57:51 +02:00
ff221fba96
Currently we validate the fee extension by summing up all fees present in the extension and comparing it against the total fee to be charged. While this works in most cases, we'd like the ability to individually validate each fee. This is especially useful during EAP when two fees are charged, a regular "create" fee that would also be amount we charge during renewal, and a one time "EAP" fee. Because we can only distinguish fees by their descriptions, we try to match the description to the format string of the fee type enums. We also only require individual fee matches when we are charging more than one type of fees, which makes the change compatible with most existing use cases where only one fees is charged and the description field is ignored in the extension. We expect the workflow to be that a registrar sends a domain check, and we reply with exactly what fees we are expecting, and then it will use the descriptions in the response to send us a domain create with the correct fees. Note that we aggregate fees within the same FeeType together. Normally there will only be one fee per type, but in case of custom logic there could be more than one fee for the same type. There is no way to distinguish them as they both use the same description. So it is simpler to just aggregate them. This CL also includes some reformatting that conforms to google-java-format output. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=186530316 |
||
|---|---|---|
| .. | ||
| operational-procedures | ||
| admin-tool.md | ||
| architecture.md | ||
| authentication-framework.md | ||
| code-structure.md | ||
| coding-faq.md | ||
| configuration.md | ||
| developing.md | ||
| first-steps-tutorial.md | ||
| flows.md | ||
| install.md | ||
| operational-procedures.md | ||
| rdap.md | ||
| rde-import-architecture.md | ||
| rde-import-usage.md | ||
| registrar-faq.md | ||