5 Commits (13b12e89408869c5b560a81e95bca33267bdb8e1)

Author	SHA1	Message	Date
Zeqing Zhang	be7c0bdce2	add testcase for aws china region	2017-11-15 16:39:47 +08:00
David McMahon	ef0c9f0c5b	Remove "All rights reserved" from all the headers.	2016-06-29 17:47:36 -07:00
Rudi Chiarito	6e6ea46182	Include changes from feedback ... Use constructor for ecrProvider Rename package to "credentials" like golint requests Don't wrap the lazy provider with a caching provider Add immedita compile-time interface conformance checks for the interfaces Added comments	2016-05-10 12:03:40 -04:00
Rudi Chiarito	eea29e8851	Allow cross-region image pulling with AWS' ECR ... This is step two. We now create long-lived, lazy ECR providers in all regions. When first used, they will create the actual ECR providers doing the work behind the scenes, namely talking to ECR in the region where the image lives, rather than the one our instance is running in. Also: - moved the list of AWS regions out of the AWS cloudprovider and into the credentialprovider, then exported it from there. - improved logging Behold, running in us-east-1: ``` aws_credentials.go:127] Creating ecrProvider for us-west-2 aws_credentials.go:63] AWS request: ecr:GetAuthorizationToken in us-west-2 aws_credentials.go:217] Adding credentials for user AWS in us-west-2 Successfully pulled image 123456789012.dkr.ecr.us-west-2.amazonaws.com/test:latest" ``` *"One small step for a pod, one giant leap for Kube-kind."*	2016-05-10 12:03:39 -04:00
Rudi Chiarito	bc0dd97a70	ECR credential provider	2016-01-22 15:03:25 -05:00