Skip to content
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.

Fix deploying to aws v4 regions #21

Merged
merged 6 commits into from
Dec 2, 2015
Merged

Conversation

andreialecu
Copy link
Contributor

This changes the deployment code to use a different package that can support v4 signatures, which are required for newer AWS regions.

See #19

@nikDemyankov
Copy link
Member

Thanks! Will test it.

@nikDemyankov nikDemyankov added this to the v1.1.0 milestone Nov 20, 2015
@nikDemyankov nikDemyankov merged commit db50d6b into nordnet:master Dec 2, 2015
@nikDemyankov
Copy link
Member

Merged, thanks!

@nikDemyankov nikDemyankov modified the milestones: v1.0.3, v1.1.0 Dec 2, 2015
@nikDemyankov
Copy link
Member

@andreialecu
After moving to s3-sync-aws package when I try to install CLI client - I get the following warning:

npm WARN EPEERINVALID [email protected] requires a peer of level@~1.3.0 but none was installed.

Warning can be removed by manually running npm install level. Some problem with dependencies in package.json in s3-sync-aws.

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

Successfully merging this pull request may close these issues.

2 participants