keystone: add v3 limits create operation#2464
Conversation
|
Thanks. Would love to see acceptance tests here as well. |
2a3be28 to
391f915
Compare
391f915 to
fe20aa5
Compare
@mandre |
check for |
|
|
FYI: I'm working on finding why are the permissions failing when |
0ef9610 to
9fc81fd
Compare
|
@mandre @EmilienM I managed to fix the test (partially). There were two issues:
|
mandre
left a comment
There was a problem hiding this comment.
Hey @emilmaruszczak, sorry for the time it took to get back to your PR. Nice find about the missing system scope (on a related note, we've just merged the ability to set the system scope in gophercloud-utils with gophercloud/utils#181 in case you need it).
Do you mind creating an issue for implementing the registered limits API calls, so that we have better context for why we skip tests for some releases?
| th.AssertNoErr(t, err) | ||
|
|
||
| // Find image service (glance on Devstack) which has precreated registered limits. | ||
| // TODO: Use registered limits API to create global limit and then overwrite it with limit. |
There was a problem hiding this comment.
I'm fine skipping these tests for versions of openstack for which our workaround doesn't work. Just make sure that we log an issue for implementing the required registered limits API calls, and we reference it here in a comment.
You can skip the tests with something like:
clients.SkipReleasesBelow(t, "stable/xena")There was a problem hiding this comment.
Did that, mentioned the todo in the existing task.
The utils clientconfig has too much logic, it's impossible to get envs that will set the system scope and domain properly. I'll write an issue on it when I have the time.
For #2289
docs
code