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

Open up API for better integration #9

Closed
Falx opened this Issue Jan 14, 2016 · 15 comments

Comments

Projects
None yet
5 participants
@Falx

Falx commented Jan 14, 2016

I am currently trying to integrate packagedrone in my continuous integration setup. It would be great to be able to access the API for some basic info.

E.g.
If I could access an overview in JSON via an endpoint of my current channels, I could show a selection box on my webpage to select to which channel the current setup should publish.

@ctron

This comment has been minimized.

Show comment
Hide comment
@ctron

ctron Jan 14, 2016

Contributor

Definitely 👍

Contributor

ctron commented Jan 14, 2016

Definitely 👍

@ctron

This comment has been minimized.

Show comment
Hide comment
@ctron

ctron Jan 14, 2016

Contributor

My initial approach would be to use [1] as a REST platform and write up a few services.

The only important part is the matter of authentication and authorization.

[1] https://github.com/hstaudacher/osgi-jax-rs-connector

Contributor

ctron commented Jan 14, 2016

My initial approach would be to use [1] as a REST platform and write up a few services.

The only important part is the matter of authentication and authorization.

[1] https://github.com/hstaudacher/osgi-jax-rs-connector

@kdoteu

This comment has been minimized.

Show comment
Hide comment
@kdoteu

kdoteu Jan 14, 2016

Contributor

In our products we are using hstaudachers jax-rs-connector it is very good for implementing a rest-api. I would recommend that.

Contributor

kdoteu commented Jan 14, 2016

In our products we are using hstaudachers jax-rs-connector it is very good for implementing a rest-api. I would recommend that.

@ctron

This comment has been minimized.

Show comment
Hide comment
@ctron

ctron Jan 14, 2016

Contributor

I just added a Google Summer of Code 2016 Idea to the list [1]. Maybe someone will volunteer 😉

[1] https://wiki.eclipse.org/Google_Summer_of_Code_2016_Ideas#Package_Drone:_Create_a_REST-based_API

Contributor

ctron commented Jan 14, 2016

I just added a Google Summer of Code 2016 Idea to the list [1]. Maybe someone will volunteer 😉

[1] https://wiki.eclipse.org/Google_Summer_of_Code_2016_Ideas#Package_Drone:_Create_a_REST-based_API

@ctron

This comment has been minimized.

Show comment
Hide comment
@ctron

ctron Jan 14, 2016

Contributor

@kdoteu we are using the same framework for Eclipse SCADA. And I do know that Eclipse SmartHome is using the same in their stack. So this would also be my first choice. But maybe there is something better out there 😉

I guess the biggest topic is the authentication and authorization area. The jax-rs-connector allows to inject a custom implementation, but you first need this implementation. And adding OAuth 2 or something like that could be a bit more effort than just registering a service with OSGi.

Contributor

ctron commented Jan 14, 2016

@kdoteu we are using the same framework for Eclipse SCADA. And I do know that Eclipse SmartHome is using the same in their stack. So this would also be my first choice. But maybe there is something better out there 😉

I guess the biggest topic is the authentication and authorization area. The jax-rs-connector allows to inject a custom implementation, but you first need this implementation. And adding OAuth 2 or something like that could be a bit more effort than just registering a service with OSGi.

@ctron

This comment has been minimized.

Show comment
Hide comment
@ctron

ctron Jan 28, 2016

Contributor

I did read an interesting post in the past. maybe this helps: http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api

Contributor

ctron commented Jan 28, 2016

I did read an interesting post in the past. maybe this helps: http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api

@Boggartfly

This comment has been minimized.

Show comment
Hide comment
@Boggartfly

Boggartfly Mar 2, 2016

@Falx I'm interested in doing this as a part of GSoC 2016. Hopefully that works out!

Boggartfly commented Mar 2, 2016

@Falx I'm interested in doing this as a part of GSoC 2016. Hopefully that works out!

@Falx

This comment has been minimized.

Show comment
Hide comment
@Falx

Falx Mar 2, 2016

@Boggartfly That would be very nice!

Falx commented Mar 2, 2016

@Boggartfly That would be very nice!

@Boggartfly

This comment has been minimized.

Show comment
Hide comment
@Boggartfly

Boggartfly Mar 2, 2016

@ctron I'm willing to volunteer as a GSoC 2016 project!

Boggartfly commented Mar 2, 2016

@ctron I'm willing to volunteer as a GSoC 2016 project!

@ctron

This comment has been minimized.

Show comment
Hide comment
@ctron

ctron Mar 2, 2016

Contributor

@Boggartfly I am happy to hear that. Let me know if you need any help.

Contributor

ctron commented Mar 2, 2016

@Boggartfly I am happy to hear that. Let me know if you need any help.

@Boggartfly

This comment has been minimized.

Show comment
Hide comment
@Boggartfly

Boggartfly Mar 2, 2016

Lets see how the proposal goes!

Boggartfly commented Mar 2, 2016

Lets see how the proposal goes!

@ctron ctron referenced this issue Apr 13, 2016

Closed

API Documentation #48

@ctron

This comment has been minimized.

Show comment
Hide comment
@ctron

ctron Jun 8, 2016

Contributor

Although this proposal was not picked, another one was. Which also does require some JAX-RS infrastructure. So although there is not API itself, the basic infrastructure for JAX-RS will be added in 0.14.0. Unless there are some CQs which get rejected.

This also paves the way to creating other remote APIs based on the same technology.

So if your are still interested I would be happy to work with you on some API.

Contributor

ctron commented Jun 8, 2016

Although this proposal was not picked, another one was. Which also does require some JAX-RS infrastructure. So although there is not API itself, the basic infrastructure for JAX-RS will be added in 0.14.0. Unless there are some CQs which get rejected.

This also paves the way to creating other remote APIs based on the same technology.

So if your are still interested I would be happy to work with you on some API.

@ctron ctron self-assigned this Jun 8, 2016

@ctron ctron added this to the v0.14.0-m1 milestone Jun 8, 2016

ctron added a commit that referenced this issue Jun 8, 2016

#9: Open up API for better integration
This patch does add the OSGi connector JAX-RS implementation including
Jersey and required dependencies.
@krishnilak

This comment has been minimized.

Show comment
Hide comment
@krishnilak

krishnilak Jun 10, 2016

Hi Jens,
Yes I would like to work on. Can I hear more info?
Thank You

On Wed, Jun 8, 2016 at 7:19 PM, Jens Reimann notifications@github.com
wrote:

Although this proposal was not picked, another one was. Which also does
require some JAX-RS infrastructure. So although there is not API itself,
the basic infrastructure for JAX-RS will be added in 0.14.0. Unless there
are some CQs which get rejected.

This also paves the way to creating other remote APIs based on the same
technology.

So if your are still interested I would be happy to work with you on some
API.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#9 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AJtfHrBUboOC5ooB9-eGguHuezAFwhTmks5qJshRgaJpZM4HEyAl
.

krishnilak commented Jun 10, 2016

Hi Jens,
Yes I would like to work on. Can I hear more info?
Thank You

On Wed, Jun 8, 2016 at 7:19 PM, Jens Reimann notifications@github.com
wrote:

Although this proposal was not picked, another one was. Which also does
require some JAX-RS infrastructure. So although there is not API itself,
the basic infrastructure for JAX-RS will be added in 0.14.0. Unless there
are some CQs which get rejected.

This also paves the way to creating other remote APIs based on the same
technology.

So if your are still interested I would be happy to work with you on some
API.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#9 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AJtfHrBUboOC5ooB9-eGguHuezAFwhTmks5qJshRgaJpZM4HEyAl
.

@ctron

This comment has been minimized.

Show comment
Hide comment
@ctron

ctron Jun 13, 2016

Contributor

@krishnilak thanks for the offer, but I actually meant @Falx, since he seemed to have a specific use case to work on.

But of course you are welcomed to help if you like.

Contributor

ctron commented Jun 13, 2016

@krishnilak thanks for the offer, but I actually meant @Falx, since he seemed to have a specific use case to work on.

But of course you are welcomed to help if you like.

@Falx

This comment has been minimized.

Show comment
Hide comment
@Falx

Falx Jun 13, 2016

Currently I only use two package drone channels in my build system, so for me this is not a priority anymore. However I look forward to any developments on the package drone project.

Falx commented Jun 13, 2016

Currently I only use two package drone channels in my build system, so for me this is not a priority anymore. However I look forward to any developments on the package drone project.

ctron added a commit that referenced this issue Jun 22, 2016

#9: Open up API for better integration - Access tokens
This change brings access tokens which can be issued like deploy keys
but on a global level to grant access to Package Drone over the remote
API.

But this is just a first step towards an authentication schema.

@ctron ctron closed this Jun 24, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment