Hi, I'm aware that there is already an AWS SDK implementation for Smalltalk ( https://github.com/newapplesho/aws-sdk-smalltalk ) This implementation doesn't seem to be a complete implementation to access all AWS services. Using a live-programming environment like Pharo would be so cool, flexible, productive and intuitive to control/ manage AWS resources - but implementing the SDK by hand is probably not a good idea, since it would be so hard to keep it up-to-date, because AWS adds new features weekly ... I contacted the AWS enterprise support and they gave me some great hints. There are many 3rd party SDK's available that utilizes the json files provided in botocore to automatically generate SDKs:
Botocore: https://github.com/boto/botocore Example service.json:https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/service-2.json They can then automatically generate an SDK based off of these json definitions. One example of this is Rusoto, the AWS SDK for Rust: Rusoto: https://github.com/rusoto/rusoto
Automatic generation portion: https://github.com/rusoto/rusoto/tree/master/service_crategen Would anyone interested in supporting this kind of project? What would be a good starting-point? Although I am (to be honest: I was) a Smalltalk-Programmer, I have too little experience with Pharo - but maybe others might find this useful. It would also be useful to "spread the word" - AWS scripting/ automation is so popular, there would be so many occasions to showcase Pharo + AWS or to create Products that are based on AWS services. Regards Stefan |
It would be cool to have some bindings.
I remember that It would be nice to make it work in Pharo 70. Now are you sure that this is complex to take json description and generate SDKs Did you run a controlled experiment? Stef
|
In reply to this post by Stefan Krecher-3
Hi,
This is interesting indeed. The meta descriptions in JSON are cool and most probably usable. It would be a huge project, though, given how many APIs/products there are, even with auto generation. A long time ago I did a AWS S3 client that is still part of Zinc HTTP Components (https://github.com/svenvc/zinc), although I believe the authentication/signing model is old now. Sven > On 27 Feb 2019, at 12:37, Stefan Krecher <[hidden email]> wrote: > > Hi, > I'm aware that there is already an AWS SDK implementation for Smalltalk ( https://github.com/newapplesho/aws-sdk-smalltalk ) > This implementation doesn't seem to be a complete implementation to access all AWS services. > Using a live-programming environment like Pharo would be so cool, flexible, productive and intuitive to control/ manage AWS resources - but implementing the SDK by hand is probably not a good idea, since it would be so hard to keep it up-to-date, because AWS adds new features weekly ... > I contacted the AWS enterprise support and they gave me some great hints. > There are many 3rd party SDK's available that utilizes the json files provided in botocore to automatically generate SDKs: > Botocore: > https://github.com/boto/botocore > Example service.json:https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/service-2.json > They can then automatically generate an SDK based off of these json definitions. One example of this is Rusoto, the AWS SDK for Rust: > Rusoto: https://github.com/rusoto/rusoto > > Automatic generation portion: > https://github.com/rusoto/rusoto/tree/master/service_crategen > > Would anyone interested in supporting this kind of project? > What would be a good starting-point? > Although I am (to be honest: I was) a Smalltalk-Programmer, I have too little experience with Pharo - but maybe others might find this useful. It would also be useful to "spread the word" - AWS scripting/ automation is so popular, there would be so many occasions to showcase Pharo + AWS or to create Products that are based on AWS services. > > Regards > Stefan |
In reply to this post by ducasse
How would a controlled experiment look like? Am Mi., 27. Feb. 2019 um 13:18 Uhr schrieb ducasse <[hidden email]>:
Dipl.-Wirtsch.-Inf. Stefan Krecher Neulander Str. 17, 27374 Visselhövede Tel +49(0)4262 958848 mobil +49(0)172 4396852 |
Take one feature and see how difficult it is to build it.
Stef
|
In reply to this post by Sven Van Caekenberghe-2
Hi, Here is yet another (very) partial implementation of an AWS SDK for Pharo: https://github.com/jvdsandt/pharo-aws-toolbox But it does have the latest (V4) signing algoritm! It would be very nice if you can generate a Pharo implemetation of an AWS service from a meta description! Jan. On Wed, Feb 27, 2019 at 2:02 PM Sven Van Caekenberghe <[hidden email]> wrote: Hi, |
In reply to this post by Stefan Krecher-3
Richard Prinz made one for Google's APIs
The code is here: https://github.com/seandenigris/St-Google-API (also Sean - maybe merge them PRs! :) ) The blog post describing what he did is here: https://www.min.at/prinz/?x=entry:entry150318-104537 Maybe Amazon publishes a similar resource you can use. Stefan Krecher-3 wrote > Hi, > I'm aware that there is already an AWS SDK implementation for Smalltalk ( > https://github.com/newapplesho/aws-sdk-smalltalk ) > This implementation doesn't seem to be a complete implementation to access > all AWS services. > Using a live-programming environment like Pharo would be so cool, > flexible, > productive and intuitive to control/ manage AWS resources - but > implementing the SDK by hand is probably not a good idea, since it would > be > so hard to keep it up-to-date, because AWS adds new features weekly ... > I contacted the AWS enterprise support and they gave me some great hints. > There are many 3rd party SDK's available that utilizes the json files > provided in botocore to automatically generate SDKs: Botocore: > https://github.com/boto/botocore > <https://github.com/boto/botocore>Example service.json: > <https://github.com/boto/botocore> > https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/service-2.json > They can then automatically generate an SDK based off of these json > definitions. One example of this is Rusoto, the AWS SDK for Rust: > Rusoto: https://github.com/rusoto/rusoto Automatic generation portion: > https://github.com/rusoto/rusoto/tree/master/service_crategen > > Would anyone interested in supporting this kind of project? > What would be a good starting-point? > Although I am (to be honest: I was) a Smalltalk-Programmer, I have too > little experience with Pharo - but maybe others might find this useful. It > would also be useful to "spread the word" - AWS scripting/ automation is > so > popular, there would be so many occasions to showcase Pharo + AWS or to > create Products that are based on AWS services. > > Regards > Stefan -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html |
Free forum by Nabble | Edit this page |