I am new to CircleCI and trying to implement a simple workflow to apply and delete my terraform infrastructure using the terraform orb. This is my .circleci/config.yml file :-
version: 2.1
orbs:
terraform: circleci/terraform#3.1
jobs:
deploy_infrastructure:
executor: terraform/default
steps:
- checkout
- terraform/init
- terraform/validate
- terraform/plan
- terraform/apply
- terraform/destroy
workflows:
deploy_infrastructure:
jobs:
- deploy_infrastructure
I am able to create the infrastructure but as soon as it gets to destroy, it fails with the following error :-
Error: Module not installed
│
│ on main.tf line 1:
│ 1: module "vpc" {
│
│ This module is not yet installed. Run "terraform init" to install all modules required by this configuration
I even added terraform/init step before the terraform/destroy step and it still fails with the same error. Any help will be appreciated.
version: '2.1'
jobs:
init:
docker:
- image: hashicorp/terraform
steps:
- checkout
- run: terraform init
- run: terraform plan
- run: terraform apply -auto-approve
- persist_to_workspace:
root: .
paths:
- .
hold:
docker:
- image: hashicorp/terraform
steps:
- run: echo "Placeholder"
destroy:
docker:
- image: hashicorp/terraform
steps:
- attach_workspace:
at: .
- run: terraform destroy -auto-approve
workflows:
test:
jobs:
- init
- hold:
type: approval
requires:
- init
- destroy:
requires:
- hold
This worked!!!
Related
Here's my code
version: 2.1
orbs:
flutter: circleci/flutter#1.1.0
jobs:
build:
working_directory: ~/project
docker:
- image: "cirrusci/flutter"
steps:
- checkout
- run: flutter main.dart
test:
working_directory: ~/project
docker:
- image: "cirrusci/flutter"
steps:
- checkout
- run: flutter widget_test.dart
workflows:
build_and_test:
jobs:
- build
- test:
requires:
- build
I got this error from the CircleCI:
Unable to parse YAML # mapping values are not allowed here # in
'string', line 3, column 5
You can use this YAML script to achieve your workflow:
# Use the latest 2.1 version of CircleCI pipeline process engine.
# See: https://circleci.com/docs/2.0/configuration-reference
version: 2.1
# Define a job to be invoked later in a workflow.
# See: https://circleci.com/docs/2.0/configuration-reference/#jobs
jobs:
build:
description: App Bundle Build
docker:
- image: cirrusci/flutter
steps:
- checkout
- run:
name: Build Flutter (Android)
command: |
flutter pub get
flutter clean
flutter build apk --release
- store_artifacts:
path: build/app/outputs/flutter-apk/app-release.apk
test:
description: Flutter App Test
docker:
- image: cirrusci/flutter
steps:
- checkout
- run:
name: Run Flutter Test and Analyze
command: |
flutter doctor
flutter pub get
flutter analyze
flutter test
workflows:
build_and_test:
jobs:
- build
- test:
requires:
- build
I'm new in circleci. I want to install my infrastructure via terraform after that I also want to trigger my build, deploy and push command for aws side. But workflow does not allow me to use plan_approve_apply and build-and-deploy together in understand one workflow. I also try to create multiple workflows (like below example) for each one but also it didn't work. How can I call both in single circli config file
My Circleci config yml file:
version: 2.1
orbs:
aws-ecr: circleci/aws-ecr#8.1.0
aws-ecs: circleci/aws-ecs#2.2.1
jobs:
init-plan:
working_directory: /tmp/project
docker:
- image: docker.mirror.hashicorp.services/hashicorp/terraform:light
steps:
- checkout
- run:
name: terraform init & plan
command: |
terraform init
terraform plan
- persist_to_workspace:
root: .
paths:
- .
apply:
docker:
- image: docker.mirror.hashicorp.services/hashicorp/terraform:light
steps:
- attach_workspace:
at: .
- run:
name: terraform
command: |
terraform apply
- persist_to_workspace:
root: .
paths:
- .
destroy:
docker:
- image: docker.mirror.hashicorp.services/hashicorp/terraform:light
steps:
- attach_workspace:
at: .
- run:
name: destroy
command: |
terraform destroy
- persist_to_workspace:
root: .
paths:
- .
workflows:
version: 2
plan_approve_apply:
jobs:
- init-plan
- apply:
requires:
- init-plan
- hold-destroy:
type: approval
requires:
- apply
- destroy:
requires:
- hold-destroy
workflows: # didn't work
build-and-deploy:
jobs:
- aws-ecr/build_and_push_image:
account-url: "${AWS_ACCOUNT_ID}.dkr.ecr.${AWS_DEFAULT_REGION}.amazonaws.com"
repo: "${AWS_RESOURCE_NAME_PREFIX}"
region: ${AWS_DEFAULT_REGION}
tag: "${CIRCLE_SHA1}"
- aws-ecs/deploy-service-update:
requires:
- aws-ecr/build_and_push_image
aws-region: ${AWS_DEFAULT_REGION}
family: "${AWS_RESOURCE_NAME_PREFIX}-service"
cluster-name: "${AWS_RESOURCE_NAME_PREFIX}-cluster"
container-image-name-updates: "container=${AWS_RESOURCE_NAME_PREFIX}-service,image-and-tag=${AWS_ACCOUNT_ID}.dkr.ecr.${AWS_DEFAULT_REGION}.amazonaws.com/${AWS_RESOURCE_NAME_PREFIX}:${CIRCLE_SHA1}"
Need to clone some repo say: git clone abc.git then switch context to abc then use the dockerfile inside abc to build using skaffold passing custom ARGS.
Is it possible to achieve this via skaffold
for eg:
- name: test-build
build:
tagPolicy:
envTemplate:
template: 1.0.0
artifacts:
- image: dockerhub.io/test-build
requires:
command: ["git", "clone", "abc.git"]
context: ./abc
This is one way that worked for me by using skaffold custom build
- name: test-build
build:
tagPolicy:
envTemplate:
template: 1.0.0
artifacts:
- image: dockerhub.io/test-build
custom:
buildCommand: docker build github.com/abc.git#v1
I have this simple config:
version: 2
jobs:
build:
machine: true
steps:
- checkout
- run: |
docker-compose -f docker-compose.test.yml build
test:
machine: true
working_directory: ~/app
steps:
- checkout
- run:
command: make test
name: Test
workflows:
version: 2
build_and_test:
jobs:
- build
- test:
requires:
- build
My test job, the second one, fails for some reasons. But whenever I check the logs on CircleCI, I can see that the image is always built in this job. I was expecting that the job would use the container that was built in the build job. So question is, why are containers not shared across jobs?
Struggling for a few last days to migrate from CircleCI 1.0 to 2.0 and while the build process is done, deployment is still a big issue. CircleCI documentation is not really of a big help.
Here is a similar config.yml to what I have:
version 2
jobs:
build:
docker:
- image: circleci/node:8.9.1
steps:
- checkout
- setup_remote_docker
- run
name: Install required stuff
command: [...]
- run:
name: Build
command: docker build -t project .
deploy:
docker:
- image: circleci/node:8.9.1
steps:
- checkout
- run:
name: Deploy
command: |
bash scripts/deploy/deploy.sh
docker tag project [...]
docker push [...]
workflows:
version: 2
build-deploy:
jobs:
- build
- deploy:
requires:
- build
filters:
branches:
only: develop
The issue is in deploy job. I have to specify the docker: -image point but I want to reuse the environment from build job where all the required stuff is installed already. Surely, I could just install them in deploy job, but having multiple deploy jobs leads to code duplication which is something I do not want.
you probably want to persist to workspace and attach it in your deploy job.
you wont need to use '- checkout' after that
https://circleci.com/docs/2.0/configuration-reference/#persist_to_workspace
jobs:
build:
docker:
- image: circleci/node:8.9.1
steps:
- checkout
- setup_remote_docker
- run
name: Install required stuff
command: [...]
- run:
name: Build
command: docker build -t project .
- persist_to_workspace:
root: ./
paths:
- ./
deploy:
docker:
- image: circleci/node:8.9.1
steps:
- attach_workspace:
at: ./
- run:
name: Deploy
command: |
bash scripts/deploy/deploy.sh
docker tag project [...]
docker push [...]
workflows:
version: 2
build-deploy:
jobs:
- build
- deploy:
requires:
- build
filters:
branches:
only: develop
If you label the image built by the build stage, you can then reference it in the deploy stage: https://docs.docker.com/compose/compose-file/#labels