securing-devops / invoicer Goto Github PK

@jvehent Hi, I'm getting the following error on the last step of the build (Test Dependencies are up to date):

#!/bin/bash -eo pipefail
GOPATH="${GOPATH_HEAD}"; ( cd ${GOPATH_BASE}/${CIRCLE_PROJECT_REPONAME} && govend -u --prune && git diff --quiet )
math/bits bad ping: unrecognized import path "math/bits" (import path does not begin with hostname)

Exited with code exit status 1
CircleCI received exit code 1

Just curious, any ideas for a workaround?

Cheers

'Out of the box' a fork of this repo will not build on CircleCI since the DOCKER_REPO environment variable is blank.

If you look at the output of the CircleCI build, under the MACHINE section, you get a subsection entitled Exporting env vars from circle.yml just before a subsection entitled Exporting env vars from project settings.

The following line in the circle.yml will therefore not evaluate as expected:

DOCKER_REPO: "$(if [ $CIRCLE_PROJECT_USERNAME == 'Securing-DevOps' ]; then echo securingdevops; else echo $DOCKER_USER; fi)"

The DOCKER_USER environment variable hasn't been set yet...

Hi,

Please pardon my ignorance. I bought the securing devops book and i am following the steps in there.

The rebuild of the circleCI job succeeded but i do not know how to go about next step below:

You can then pull and run the container from your repository as follows:

$ docker run -it /invoicer

where do i put in the above command? I have tried to download Docker CLI but it isnt working.

Please advise.

Regards,

Ade

Hi,

When I try to run:

aws elasticbeanstalk create-environment --application-name invoicer --environment-name invoicer-api --description "Invoicer АРР" --solution-stack-name "64bit Amazon Linux 2018.03 v2.16.3 running Docker 19.03.13-ce" --option-settings file://$(pwd)/ebs-options.json --tier "Name=WebServer,Type=Standard,Version=' '"

the following error has occurred:
Environment must have instance profile associated with it.

After adding to the 'invoicer/ebs-options.json ' the following section:
{ "Namespace": "aws:autoscaling:launchconfiguration", "OptionName": "IamInstanceProfile", "Value": "aws-elasticbeanstalk-ec2-role" }

the following error has appeared:
The instance profile aws-elasticbeanstalk-ec2-role associated with the environment does not exist.

Could you clarify what instance profile I should use?

Thank you.