Page MenuHomePhabricator

Make PhutilAWSEC2Future signs requests correctly
ClosedPublic

Authored by epriestley on Nov 29 2016, 10:39 PM.
Tags
None
Referenced Files
F15532352: D16963.id40822.diff
Wed, Apr 23, 3:37 PM
F15509115: D16963.id40823.diff
Wed, Apr 16, 9:44 AM
F15506276: D16963.id.diff
Tue, Apr 15, 9:53 AM
F15455987: D16963.diff
Sun, Mar 30, 6:15 AM
F15428581: D16963.diff
Mar 23 2025, 9:14 PM
F15411303: D16963.diff
Mar 19 2025, 8:59 AM
F15411248: D16963.diff
Mar 19 2025, 8:56 AM
F15411196: D16963.diff
Mar 19 2025, 8:54 AM
Subscribers
None

Details

Summary

I partially automated a bit of provisioning stuff; the signature algorithm for EC2 is slightly different from the algorithm for S3.

Test Plan

Used bin/provision ... in rCORE to create and attach device volumes in the Phacility cluster.

Diff Detail

Repository
rPHU libphutil
Branch
ec1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 14710
Build 19220: Run Core Tests
Build 19219: arc lint + arc unit

Event Timeline

epriestley retitled this revision from to Make PhutilAWSEC2Future signs requests correctly.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Nov 29 2016, 10:57 PM
This revision was automatically updated to reflect the committed changes.