Hello,
I’m currently in the process of writing the circle.yml and deployment script to deploy our Node.js-based docker image onto AWS Elastic Beanstalk. This is what I have so far as the circle.yml.
machine:
services:
- docker
node:
version: 4.2.3
environment:
DOCKER_USER: XXXXXXXXX
DOCKER_PASS: XXXXXXXXX
AWS_ACCESS_KEY_ID: XXXXXXXXX
AWS_SECRET_ACCESS_KEY: XXXXXXXXX
AWS_DEFAULT_REGION: XXXXXXXXX
dependencies:
pre:
- pip install awscli
- docker build -t stanza/worker:$CIRCLE_SHA1 .
deployment:
production:
branch: production
commands:
- docker login -u $DOCKER_USER -p $DOCKER_PASS
- ./deploy.sh $CIRCLE_SHA1 $AWS_SECRET_ACCESS_KEY $AWS_SECRET_ACCESS_KEY $AWS_DEFAULT_REGION
My build is currently failing at the npm install section due to “access rights” issues (it runs the pre dependencies steps fine). The root cause is likely because we have a npm dependency that’s actually a private github repo. Since I’ve allowed CircleCI access to Github, shouldn’t there not be a permissions problem? Is there a way to mitigate this?
I’ve also tried instructions on
https://circleci.com/docs/permissions-and-access-during-deployment/
by adding a SSH key for allowing access to our Github repos. Still having the same error.
