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

Bring AWS CloudFront API Models/Requests up to date #3115

Closed
CpuID opened this issue Aug 19, 2014 · 5 comments
Closed

Bring AWS CloudFront API Models/Requests up to date #3115

CpuID opened this issue Aug 19, 2014 · 5 comments

Comments

@CpuID
Copy link

CpuID commented Aug 19, 2014

Heaps of missing functionality, specifically around the use of Price Classes, Custom/Dedicated SSL certificates, etc.

Current API version is 3~ years behind, has some authentication breakage when you try and just change the version to 2014-05-31:

 response => #<Excon::Response:0x007f991daab9b0 @data={:body=>"<?xml version=\"1.0\"?>\n<ErrorResponse xmlns=\"http://cloudfront.amazonaws.com/doc/2014-01-31/\"><Error><Type>Sender</Type><Code>IncompleteSignature</Code><Message>Authorization header requires 'Credential' parameter. Authorization header requires 'Signature' parameter. Authorization header requires 'SignedHeaders' parameter.
@CpuID
Copy link
Author

CpuID commented Aug 19, 2014

I am will to go through and try make the require changes, but I will need some coaching on some of the Fog internals to do so...

@geemus
Copy link
Member

geemus commented Aug 19, 2014

@CpuID happy to help as you need it. Probably just need to switch from v3 signatures to v4 (at a guess). I think maybe EC2 (aws compute) already uses v4 if you need a point of reference.

@fcheung
Copy link
Contributor

fcheung commented Nov 8, 2014

I had a quick look this afternoon - switching signature versions is easy enough but the change of api version changes the xml returned by some of the existing requests (eg get_distribution_list) in a way that stops the existing parser from processing it). There are what seem to be some quite substantial changes to the data returned, so this could in turn break users of the existing models/code. Definitely more work than just upgrading signatures and bumping api versions

@geemus
Copy link
Member

geemus commented Nov 11, 2014

@fcheung thanks for the update. Hopefully somebody with the interest/time can dig deeper on this one.

@plribeiro3000
Copy link
Member

Closed in favor of fog/fog-aws#17

@fog fog locked and limited conversation to collaborators Jan 15, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants