search

weaveworks / integrations

Weave Third-Party Integrations
Apache License 2.0
26 stars 22 forks source link

Travis build fails because "unable to locate credentials". #138

Open dholbach opened 6 years ago

dholbach commented 6 years ago

Travis build for #137 (https://travis-ci.org/weaveworks/integrations/builds/366114204) fails like so:

$ aws cloudformation validate-template --template-body "file:////${PWD}/aws/ecs/cloudformation.json" | jq .
Unable to locate credentials. You can configure credentials by running "aws configure".
The command "aws cloudformation validate-template --template-body "file:////${PWD}/aws/ecs/cloudformation.json" | jq ." exited with 255.
1.39s$ aws cloudformation validate-template --template-body "file:////${PWD}/aws/ecs/cloudformation-no-app.json" | jq .
Unable to locate credentials. You can configure credentials by running "aws configure".
The command "aws cloudformation validate-template --template-body "file:////${PWD}/aws/ecs/cloudformation-no-app.json" | jq ." exited with 255.
1.38s$ aws cloudformation validate-template --template-body "file:////${PWD}/aws/ecs/cloudformation-larger-app.json" | jq .
Unable to locate credentials. You can configure credentials by running "aws configure".
The command "aws cloudformation validate-template --template-body "file:////${PWD}/aws/ecs/cloudformation-larger-app.json" | jq ." exited with 255.
1.40s$ aws cloudformation validate-template --template-body "file:////${PWD}/aws/ecs/cloudformation-identiorca.json" | jq .
Unable to locate credentials. You can configure credentials by running "aws configure".
The command "aws cloudformation validate-template --template-body "file:////${PWD}/aws/ecs/cloudformation-identiorca.json" | jq ." exited with 255.
bboreham commented 6 years ago

@errordeveloper how is this supposed to work?

What is the Travis build even supposed to do? Looks like a half-implemented step towards stopping publishing AMIs?

errordeveloper commented 6 years ago

There are supposed to be secrets in Travis, maybe those got removed from AWS or somehow else got invalidated...?

What Travis was supposed to do is validate CloudFormation temolates, and publish them to S3. I had no intention to fully automate building the AMI directly from Travis, becuase it is complicated, unless someone else tried to implement that.

On Fri, 15 Jun 2018, 2:01 am Bryan Boreham, notifications@github.com wrote:

@errordeveloper https://github.com/errordeveloper how is this supposed to work?

What is the Travis build even supposed to do? Looks like a half-implemented step towards stopping publishing AMIs?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/weaveworks/integrations/issues/138#issuecomment-397559496, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPWS8rIm_itXAkkJ_OJqeQEOZjVdGHVks5t83ftgaJpZM4TTegM .