-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to check which series can be read/ written #648
How to check which series can be read/ written #648
Conversation
Hi @nicolai86, I believe this was left out when permissions where added. We love prs. Let us know if you need help with it. |
@jvshahid I've finished a first draft, tests seem to pass & manual testing indicates that the attributes are returned correctly. However I'd like some feedback regarding coding style & general structure, as I might've been going down the wrong path while implenting the changes... |
@nicolai86 can you sign the cla at http://influxdb.com/community/cla.html so we can merge the pr. I'll take a look at the pr now |
lgtm. Ideally I'd like to see a test to go with the pr. A test would probably require changing the go client library which we use in the tests. If you feel like making that change as well, it'd be awesome. The assertion should probably be in this test |
Also, the test suite failed. Can you run |
Looks like I missed some instances of the changed struct initialisation. Didn't see that >.< |
odd, looks like |
yeah, travis run the integration tests as well, I asked you to run make test because the unit tests were failing and is much faster to run |
integration tests really are quite slow... |
and off I go again, fixing the slow tests :) |
@nicolai86 it looks like the only test that's currently failing is |
you can add |
Ah thanks for the info I was looking for that. will fix it in a second |
Didn't know how to run a single integration test |
@jvshahid thanks for the heads up, I'm new to golang tests /w tags (e.g. integration) and the codebase is bigger than most of my golang projects! |
yay tests are green. Now back any other feedback you might have? |
Closed by e5de7d3 |
When creating new database users the cluster admin can set readFrom/ writeTo attributes.
However these attributes are not returned when executing
GET /db/anydb/users
.This makes maintaining granular series permissions a problem because I don't know which permissions a user currently has.
Now I'm wondering: was this by design, or did you just leave this out for a later point in time? Would you accept PR's which add these attributes to UserDetails ?