Make it possible to locally test common-packer 76/8276/2
authorThanh Ha <thanh.ha@linuxfoundation.org>
Fri, 5 Jan 2018 20:48:22 +0000 (15:48 -0500)
committerThanh Ha <thanh.ha@linuxfoundation.org>
Sat, 6 Jan 2018 01:55:39 +0000 (20:55 -0500)
By symlinking common-packer to itself this makes it possible to test
common-packer from it's own project repo.

Change-Id: I022b63aeab561815da3e8856f195201b668cfed0
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
README.markdown
common-packer [new symlink]

index 57ad0e5..aa4e0cc 100644 (file)
@@ -92,3 +92,10 @@ Steps 1-3 are actually all contained inside of the local playbook. Please refer
 to the docker template and provisioning script for an example of how it imports
 the existing baseline playbook into the local playbook to reduce duplication in
 code.
+
+## Local testing of common-packer
+
+For developers of common-packer who would like to be able to locally test from
+the common-packer repo. Clone both common-packer and lf-ansible in the same
+directory and the scripts will handle the relative paths to both itself
+(common-packer) and lf-ansible respectively.
diff --git a/common-packer b/common-packer
new file mode 120000 (symlink)
index 0000000..945c9b4
--- /dev/null
@@ -0,0 +1 @@
+.
\ No newline at end of file