You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Again, the usage is recorded successfully, although there is no unitType=dummy in the catalog.
The text was updated successfully, but these errors were encountered:
reshmabidikar
changed the title
KB allows recording a usage with the wrong unittype
KillBill allows recording a usage with the wrong unit type
May 2, 2024
So summarising the ticket...a subscription based on a server-monthly-standard plan defined in the above catalog currently allows data submitted to the /1.0/kb/usages api to:
Record usage for usage unit type not defined in plan : submitted value [unitType=server-hourly-type-2]
Record usage for usage unit type not defined in catalog : submitted value [unitType=dummy]
May I suggest for clarity we rename the issue Recording usage only using defined unit types - improve unit type validation checks
Also what are the implications on the billing cycle ? Do they result in invoice items being generated or are they ignored?
Validation failures should also return an appropriate error code indicating which validation check they failed.
Steps to reproduce:
server-monthly-standard
plan (usesserver-hourly-type-1
unitType)unitType=server-hourly-type-2
as follows:The usage is recorded successfully. Expected Behavior: An error should be displayed indicating that the wrong unit is specified.
unitType=dummy
as follows:Again, the usage is recorded successfully, although there is no
unitType=dummy
in the catalog.The text was updated successfully, but these errors were encountered: