Skip to content
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

Full CRUD Admin API #152

Closed
19 of 20 tasks
brylie opened this issue Jun 8, 2015 · 6 comments
Closed
19 of 20 tasks

Full CRUD Admin API #152

brylie opened this issue Jun 8, 2015 · 6 comments

Comments

@brylie
Copy link
Contributor

brylie commented Jun 8, 2015

Add full CRUD (Create, Read, Update, Delete) methods to Admin API for all API Umbrella data objects.

User Story

As an application developer
I would like to have full CRUD methods for all API Umbrella data objects
so that I can fully integrate my application with the API Umbrella platform

Definition of done

API Users

API Backends

Admin Users

API Scopes

  • Create
  • Read
  • Update
  • Delete

Admin Groups

  • Create
  • Read
  • Update
  • Delete
@GUI
Copy link
Member

GUI commented Jun 9, 2015

Thanks for pulling this together as a cohesive list! Nothing quite like checkboxes to make it clear what's missing. :)

We do already have CRU[D] APIs (well, lacking the deletes like seemingly most everything else) for API Scopes at /api-umbrella/v1/api_scopes and Admin Groups at /api-umbrella/v1/admin_groups. But I'll try to get the DELETEs implemented everywhere soon and finally, finally get all the API documentation updated on all this.

@brylie
Copy link
Contributor Author

brylie commented Jun 9, 2015

@GUI thanks for the quick response. We have another issue open regarding the documentation, with the idea to produce a Swagger or RAML description of the Admin API. What do you think of the Swagger/RAML description file idea?

@GUI
Copy link
Member

GUI commented Jun 27, 2015

@brylie: Sorry again for the delays. I believe I've added all the missing CRUD endpoints in master (NREL/api-umbrella-web@fafa1a8) with the exception of a DELETE action for users. However, users can be disabled, which should effectively be the same.

If you do want to delete users, let me know, since that would be helpful to know. We can certainly add delete capabilities, there's just a bit more to figure out (mainly soft deletes vs hard deletes, but also analytics implications).

And I definitely like the idea of a RAML or Swagger specification for all these API endpoints. I was hoping to get that those docs fully written for all of these endpoints as part of this update, but unfortunately I haven't gotten that done and I'll be without much internet access for the next couple weeks. So it will be a few weeks before I can circle back to this, but I do really want to get the docs updated so all of this is more clearly documented. Do you have any preferences on RAML vs Swagger, or does either one suit you?

@brylie
Copy link
Contributor Author

brylie commented Jul 1, 2015

@GUI can we please discuss the Admin API documentation in the related issue?

@GUI
Copy link
Member

GUI commented Jul 29, 2015

I'm going to go ahead and close this since the missing DELETE endpoints have been added and the documentation has been updated.

@sandeepkottagundu
Copy link

I creating user using postman tool it will created user successfully but it will calll in my front end application it will give 403 error(Response for preflight has invalid HTTP status code 403) please give response as soon as possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants