;openstack@lists.openstack.org"
> Subject: Re: [Openstack] [openstack-dev] About fix of validate name
> string length at API level
> Message-ID:
>com>
> Content-Type: text/plain; charset="utf-8"
>
> I think as we start moving these vali
I think as we start moving these validations to the API, we should probably
just enforce them across all plugins. Having conditionals in the API to
check if the DB is there to change validation logic doesn't sound like much
fun to maintain.
On Thu, Feb 5, 2015 at 1:22 AM, Akihiro Motoki wrote:
>
It is a good idea to enforce some validations for string fields.
As Kevin said, Contrail plugin does not use db-backend but the API
layer is still used,
so attrbiutes.py works in the API layer, so we need to coordinate the effort.
In addition, Neutron API v2.0 is an already shipped version. so we
To: Kevin Benton
To: Mark McClain,
Cc: Akihiro Motoki
Hello, Kevin Benton. Thank you for the reply.
I have an idea.
If there is a DB that can be detected (something like sql.true()), we set 255
to name validate, otherwise we leave it as None.
How do you like this idea?
Best regards,
watanabe.is
