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
{{ message }}
Repository navigation
Empty spec.resource.name falls back to metadata.name which is too long #1058
> k get projectNAME ID AVAILABLE MESSAGExo1yjslpzk5kmve94tkoc0bymm3u9dqcd7i2qsiahpcp2c4eh17teq9vylui0lypm False Expected HTTP response code [201 202] when accessing [POST http://10.0.79.110/identity/v3/projects], but got 400 instead: {"error":{"code":400,"message":"Invalid input for field/attribute name. Value: xo1yjslpzk5kmve94tkoc0bymm3u9dqcd7i2qsiahpcp2c4eh17teq9vylui0lypm. 'xo1yjslpzk5kmve94tkoc0bymm3u9dqcd7i2qsiahpcp2c4eh17teq9vylui0lypm' is too long","title":"Bad Request"}}
This is database detail that I think it can't be discovered via services API. I think we could have a new option in the resource-generator or scaffolding-controller to enforce that at the API level.
Activity
winiciusallan commentedon Nov 12, 2026
This is database detail that I think it can't be discovered via services API. I think we could have a new option in the resource-generator or scaffolding-controller to enforce that at the API level.