a49f3a04d0
The calculate_usage interface was added recently to allow consumers to probe limits and usage without requiring the enforce behavior workflow. If a limit was passed to it that was not registered in keystone, get_project_limits() would raise a ProjectOverLimit exception itself to abort the process immediately, providing the "unregistered means zero" behavior. This works fine for the enforce workflow, but not the calculate one. This changes get_project_limits() to just return a zero limit for a missing one, which will be considered by the enforce workflow in the same way, keeping the existing behavior. It will merely be reported by the calculate workflow, which is the desired change. Change-Id: Iaab1f0d5eb0da9a667267537d86f6c70bc8db51d |
||
|---|---|---|
| .. | ||
| index.rst | ||
| testing.rst | ||
| usage.rst | ||