-
Notifications
You must be signed in to change notification settings - Fork 488
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
3358 api cleanup #3381
3358 api cleanup #3381
Conversation
… spec. Code cleanup
…for Dataverses resource class.
# Conflicts: # src/main/java/edu/harvard/iq/dataverse/api/Groups.java # src/main/java/edu/harvard/iq/dataverse/authorization/groups/impl/ipaddre ss/IpGroup.java
Conflicts: src/test/java/edu/harvard/iq/dataverse/api/DataversesIT.java Just imports and whitespace.
…patibility, Guide updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@michbarsinai can you please list #3209 in your pull request (#3381)? And any other issues the pull request addresses. There's also magic "Connects to" syntax at the bottom that should be updated to that issues are associated with pull requests at https://waffle.io/IQSS/dataverse
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only question is why we moved the test api to be under admin. Will discuss with MBS and others, shouldn't stop QA from happening.
Because right now we are scaring the poor sysadmins unnecessarily: http://guides.dataverse.org/en/4.4/installation/config.html#blocking-api-endpoints says, "There is a “test” API endpoint used for development and troubleshooting that has some potentially dangerous methods." |
Also, blocking the "admin" API is more than a good idea. It's essential. Fixed the wording.
RFI Checklist
Before submitting the pull request, fill out sections (1.) Related Issues and (2.) Pull Request Checklist.
1. Related Issues
/api/test
endpoint2. Pull Request Checklist
3. Review Checklist
After the pull request has been submitted, fill out this section.
connects to #3358
connects to #3209
connects to #3250
connects to #3235