Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
A
ansible
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
OpenEdx
ansible
Commits
923c1720
Commit
923c1720
authored
May 21, 2014
by
Anton Lindström
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Enabled integration tests for encrypted vars in Makefile
parent
926755c3
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
1 deletions
+7
-1
test/integration/Makefile
+7
-1
No files found.
test/integration/Makefile
View file @
923c1720
...
...
@@ -14,7 +14,9 @@ else
CREDENTIALS_ARG
=
endif
all
:
non_destructive destructive check_mode test_hash test_handlers test_group_by
VAULT_PASSWORD_FILE
=
vault-password
all
:
non_destructive destructive check_mode test_hash test_handlers test_group_by test_var_in_vault
non_destructive
:
ansible-playbook non_destructive.yml
-i
$(INVENTORY)
-e
@
$(VARS_FILE)
$(CREDENTIALS_ARG)
-v
$(TEST_FLAGS)
...
...
@@ -38,6 +40,10 @@ test_hash:
test_var_precedence
:
ansible-playbook test_var_precedence.yml
-i
$(INVENTORY)
$(CREDENTIALS_ARG)
-v
-e
'extra_var=extra_var'
test_var_in_vault
:
ansible-playbook test_var_in_vault.yml
-i
$(INVENTORY)
$(CREDENTIALS_ARG)
-v
$(TEST_FLAGS)
--vault-password-file
$(VAULT_PASSWORD_FILE)
--list-tasks
ansible-playbook test_var_in_vault.yml
-i
$(INVENTORY)
$(CREDENTIALS_ARG)
-v
$(TEST_FLAGS)
--vault-password-file
$(VAULT_PASSWORD_FILE)
cloud
:
amazon rackspace
cloud_cleanup
:
amazon_cleanup rackspace_cleanup
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment