Repository navigation
RegisteredLimit does not allow a defaultLimit of 0 #3866
Description
What happened?
The defaultLimit field for RegisteredLimits in Gophercloud is an integer with required:true
While OpenStack permits a value of 0, Gophercloud will fail validation for the field in that case.
Gophercloud runs into this:
Lines 92 to 97 in 7544537
Expected behavior would be that Gophercloud permits requests containing a defaultLimit of 0 (in fact everything from -1 to 2147483647 should be valid)
See also k-orc/openstack-resource-controller#782 (comment)
Version
v2 (current)
Activity
gndrmnn commentedon Jul 28, 2026
I have grepped over this repo and it appears that
defaultLimitmight actually be the only field in the entire API which 1) is of the typeint2) isrequired: trueand 3) were upstream accepts a0as a valid value.So how do we even approach this? Add a new Go struct tag for this case? e.g.
numericZeroAllowed: true?winiciusallan commentedon Jul 28, 2026
The
param.gois quite old and I'm unsure the reason for skipping the zero-value when required. This surfaces some incompatibility with the expected result. I would say that we can:I personally prefer the option 1. Adding a new tag may work, but IMHO we would be putting a plaster on the real problem.