@@ -117,7 +117,7 @@ jobs:
117117 docker logs ${{ needs.build.outputs.INSTANCE_NAME }}
118118 echo TFSTATE=$(curl -sS http://localhost:2442/?env=InT) | tee -a $GITHUB_ENV
119119
120- echo -n "RESULTS=${{ env.RESULTS}}|Happy Path|✅ Success|" | tee -a $GITHUB_ENV
120+ echo -e "RESULTS=${{ env.RESULTS}}\n |Happy Path|✅ Success|" | tee -a $GITHUB_ENV
121121
122122 - name : Validate Terraform State
123123 # Validate that Terraform state saved in PyTerraBackTYL matches the content of the file generated by Terraform
@@ -129,7 +129,7 @@ jobs:
129129 echo ${TF_CONTENT} != ${FILE_CONTENT} >&2
130130 exit 1
131131 fi
132- echo "RESULTS=${{ env.RESULTS}}|State Saved|✅ Success|" | tee -a $GITHUB_ENV
132+ echo -e "RESULTS=${{ env.RESULTS}}\n |State Saved|✅ Success|" | tee -a $GITHUB_ENV
133133
134134 - name : Validate Terraform State Changed
135135 # The ID of the null resource should change with every apply. Verify PyTerraBackTYL is saving the updated state
@@ -141,7 +141,7 @@ jobs:
141141 [ -n "${NEW_NULL_RESOURCE_ID}" ]
142142 [ -n "${CURRENT_NULL_RESOURCE_ID}" ]
143143 [ "${CURRENT_NULL_RESOURCE_ID}" -ne "${NEW_NULL_RESOURCE_ID}" ]
144- echo "RESULTS=${{ env.RESULTS}}|State Changed|✅ Success|" | tee -a $GITHUB_ENV
144+ echo -e "RESULTS=${{ env.RESULTS}}\n |State Changed|✅ Success|" | tee -a $GITHUB_ENV
145145
146146 - name : Run Terraform Test, Locked ENV
147147 # Manually lock the environment and capture how terraform exited
@@ -157,7 +157,7 @@ jobs:
157157 run : |
158158 if [ "${{ steps.prelock_InT.outcome }}" != "success" ]; then
159159 curl -X UNLOCK -sS http://localhost:2442/unlock?env=InT
160- echo "RESULTS=${{ env.RESULTS}}|Locked Environment is Blocking|✅ Success|" | tee -a $GITHUB_ENV
160+ echo -e "RESULTS=${{ env.RESULTS}}\n |Locked Environment is Blocking|✅ Success|" | tee -a $GITHUB_ENV
161161 else
162162 # Picked confusing wording just to be silly
163163 echo "Step unexpectedly failed to fail as expected."
0 commit comments