version: 0.2

env:
  variables:
    GOROOT: "/usr/local/go"
    GO111MODULE: "on"
    GOARCH: "amd64"
    GOOS: "linux"
    PUBLISHERS: "inner-products variant-branches"

phases:
  install:
    runtime-versions:
      golang: 1.12
    commands:
      # AWS Codebuild Go images use /go for the $GOPATH so let's copy our
      # application source code into that directory structure.
      # Print all environment variables (handy for AWS CodeBuild logs)
      # - env | sort # BAM: We don't need to see this on every build so comment it out
      # Install golint
      # go get -u github.com/golang/lint/golint

  pre_build:
    commands:
      # - cd $CODEBUILD_SRC_DIR # BAM: We don't need to cd into the folder here, and then again inside the for loop?
      # - mkdir -p $CODEBUILD_SRC_DIR/bin
      - |
        for publisher in $PUBLISHERS; do
          # cd "${CODEBUILD_SRC_DIR}" # BAM: Do we need to cd here to do the following ln? I don't see a need to cd?
          ln -s "${CODEBUILD_SRC_DIR}/${publisher}" "/go/src/${publisher}"
          cd /go/src/${publisher}
          # pwd; ls -alF # BAM: We don't need to see this everytime
          # go get -t ./...
          go mod download
          #golint -set_exit_status
          go vet .
          go test .
        done

  build:
    commands:
      # - cd $CODEBUILD_SRC_DIR # BAM: Do we need to cd again?
      # - mkdir -p $CODEBUILD_SRC_DIR/bin
      - |
        for publisher in $PUBLISHERS; do
          cd /go/src/${publisher}
          # echo "Building '${publisher}' in `pwd`..." # BAM: Don't really need this echo cluttering the output do we?
          # go get github.com/aws/aws-lambda-go/lambda # BAM: Do we need to go get this specific library? we are using mod everywhere else, and we also include this library in our go application, which is pulled using the go mod download on line 34
          # go get -t ./...
          # go mod download # BAM: Do we really need to do a go mod download again?
          GOOS=linux go build -o $CODEBUILD_SRC_DIR/${publisher}/main # BAM: Should this just be at the end of the loop on line 37.5? I don't see a need to do another loop just for this?
        done

  post_build:
    commands:
      - cd $CODEBUILD_SRC_DIR # BAM: Do we need to cd into this folder? I think we might so leaving it
      - aws cloudformation package --template-file samLambdaTemplate.yaml --s3-bucket ${S3_BUCKET} --kms-key-id ${SAM_KEY} --output-template-file packaged-template.yaml

artifacts:

  files:
    - packaged-template.yaml
    # BAM: The below files are not needed to zip up into the artifact because the CFN stack loads those files into a secret
         # black magic S3 folder location and somehow links the Lambdas to those.
    # - inner-products
    # - variant-branches
    # "**/*"