Skip to content

Commit

Permalink
#41 Right now, Molecule v3 doesn't support AWS EC2 module - so we nee…
Browse files Browse the repository at this point in the history
…d to use Docker driver/scenario only for now
  • Loading branch information
jonashackt committed Feb 24, 2020
1 parent 861c1ba commit 968b58a
Showing 1 changed file with 14 additions and 14 deletions.
28 changes: 14 additions & 14 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,11 @@ jobs:
sudo pip install pipenv
pipenv install
# - run:
# name: Run Molecule Testing CircleCI-locally with Docker
# command: |
# cd docker
# pipenv run molecule test
- run:
name: Run Molecule Testing CircleCI-locally with Docker
command: |
cd docker
pipenv run molecule test
- run:
name: configure AWS CLI
Expand All @@ -35,15 +35,15 @@ jobs:
pipenv run aws configure set default.region ${EC2_REGION}
pipenv run aws configure list
- run:
name: Run Molecule Testing on AWS EC2
command: |
cd docker
pipenv run molecule --debug destroy --scenario-name aws-ec2-ubuntu
pipenv run molecule --debug create --scenario-name aws-ec2-ubuntu
pipenv run molecule --debug converge --scenario-name aws-ec2-ubuntu
pipenv run molecule --debug verify --scenario-name aws-ec2-ubuntu
pipenv run molecule --debug destroy --scenario-name aws-ec2-ubuntu
# - run:
# name: Run Molecule Testing on AWS EC2
# command: |
# cd docker
# pipenv run molecule --debug destroy --scenario-name aws-ec2-ubuntu
# pipenv run molecule --debug create --scenario-name aws-ec2-ubuntu
# pipenv run molecule --debug converge --scenario-name aws-ec2-ubuntu
# pipenv run molecule --debug verify --scenario-name aws-ec2-ubuntu
# pipenv run molecule --debug destroy --scenario-name aws-ec2-ubuntu

# To use a scheduled execution in CircleCI, we need to introduce a workflow
# see https://circleci.com/docs/2.0/triggers/#scheduled-builds
Expand Down

0 comments on commit 968b58a

Please sign in to comment.